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-212427 | LS on security aspects for the method of collection of data from the UE |
LS in LS reply in S3-213271, S3-212679, S3-213271 |
S2-213263 |
S3-104-e AI: 5.16 |
replied to | [WTS] [JSN] | |||
S3-212630 | add evaluation for solution#3 |
pCR revised to S3-213113 |
Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212631 | update evaluation for solution#13 | pCR | Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212632 | resovle EN for solution#3 | pCR | Huawei,HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212639 | Solution on Authorization of Data Consumers for data access via DCCF | pCR | Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212657 | Conclusion on key issue #1.2 |
pCR revised to S3-213124 |
Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212658 | Update to solution #14 to ML restrictive transfer of ML models | pCR | Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212659 | Conclusion on key issue #3.3 on restrictive transfer of ML models | pCR | Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212660 | Udpates to key issue #3.1 on attacker model | pCR | Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212661 | Conclusion on key issue #3.2 on protection of UE data in transit |
pCR revised to S3-213125 |
Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212679 | Reply-LS on security aspects for the method of collection of data from the UE |
LS out LS is reply to S3-212427 LS To: SA WG2 revised to S3-213271 |
Guangdong OPPO Mobile Telecom. | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] | ||
S3-212812 | Solution to abnormal behaviour detection of IoT SIM card | pCR | China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212813 | Add conclusion to KI #1.2 | pCR | China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
merged | [WTS] [JSN] |
S3-212814 | Add conclusion to KI #1.5 | pCR | China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212815 | Add conclusion to KI #2.1 | pCR | China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212816 | Add conclusion to KI #3.2 | pCR | China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
merged | [WTS] [JSN] |
S3-212817 | Add evaluation to solution #3 | pCR | China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
merged | [WTS] [JSN] |
S3-212818 | Discussion on the conclusion of KI#1.3 | discussion | China Mobile | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] | |
S3-212978 | Ed Note Removal for Solution 11 |
pCR revised to S3-213048 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212979 | Ed Note Removal to include mechanism when notification sent via MFAF for Solution 11 |
pCR revised to S3-213052 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212980 | Evaluation to the Solution 11 |
pCR revised to S3-213051 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212981 | Ed Note Removal for Solution 10 |
pCR revised to S3-213039 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212982 | Conclusion to KI 1.3 |
pCR revised to S3-213050 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212983 | Evaluation to the Solution 10 |
pCR revised to S3-213044 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212984 | Editorial Notes Removal for Solution 10 to address authorization mechanisms when data is sent via MFAF |
pCR revised to S3-213041 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212985 | Enhancement to the solution on Detection of anomalous NF behaviour by NWDAF | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212986 | Evaluation to the Solution 7 |
pCR revised to S3-213047 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212987 | Conclusion to KI 2.2 | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212988 | Evaluation on Sol 14 - Solution to ML restrictive transfer Framework | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212989 | Update KI 3.3 - Ensuring restrictive transfer of ML models between authorized NWDAF instances |
pCR revised to S3-213046 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212990 | Evaluation on Sol 5- Providing the Security protection of data via Messaging Framework | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212991 | Update to KI 1.4 | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
merged | [WTS] [JSN] |
S3-212992 | Conclusion to KI 1.4 | pCR | Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-212993 | Solution on Protection of data sent via MFAF using existing SBA mechanisms |
pCR revised to S3-213045 |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212994 | LS on NF Service Producer Meta Data Addition by ADRF |
LS out LS To: SA2 |
Nokia, Nokia Shanghai Bell | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] | ||
S3-212995 | Removal of Editor’s Note of Solution#4 | pCR | Lenovo, Motorola Mobility | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-212996 | Adding Evaluation to Solution#4 |
pCR revised to S3-213064 |
Lenovo, Motorola Mobility | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-212997 | Removal of Editor’s Note of Solution#5 | pCR | Lenovo, Motorola Mobility | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
merged | [WTS] [JSN] |
S3-212998 | Adding Evaluation to Solution#5 | pCR | Lenovo, Motorola Mobility | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
merged | [WTS] [JSN] |
S3-213015 | Update_on_Key_issue#1.4 |
pCR revised to S3-213152 |
Ericsson | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-213016 | Update_on_Solution#5 |
pCR revised to S3-213154 |
Ericsson | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-213017 | Update_on_Solution#12 |
pCR revised to S3-213153 |
Ericsson | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
revised | [WTS] [JSN] |
S3-213018 | Conclusion on KI#1.3 | pCR | Ericsson | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-213019 | Conclusion on KI#1.4 | pCR | Ericsson | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
noted | [WTS] [JSN] |
S3-213039 | Ed Note Removal for Solution 10 |
pCR revision of S3-212981 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213041 | Editorial Notes Removal for Solution 10 to address authorization mechanisms when data is sent via MFAF |
pCR revision of S3-212984 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213044 | Evaluation to the Solution 10 |
pCR revision of S3-212983 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213045 | Solution on Protection of data sent via MFAF using existing SBA mechanisms |
pCR revision of S3-212993 |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213046 | Update KI 3.3 - Ensuring restrictive transfer of ML models between authorized NWDAF instances |
pCR revision of S3-212989 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213047 | Evaluation to the Solution 7 |
pCR revision of S3-212986 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213048 | Ed Note Removal for Solution 11 |
pCR revision of S3-212978 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213050 | Conclusion to KI 1.3 |
pCR revision of S3-212982 |
Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213051 | Evaluation to the Solution 11 |
pCR revision of S3-212980 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213052 | Ed Note Removal to include mechanism when notification sent via MFAF for Solution 11 |
pCR revision of S3-212979 |
Nokia, Nokia Shanghai Bell | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213064 | Adding Evaluation to Solution#4 |
pCR revision of S3-212996 |
Lenovo, Motorola Mobility | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213094 | draft TR 33.866 0.6.0 | draft TR | China Mobile Com. Corporation | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] | |
S3-213113 | add evaluation for solution#3 |
pCR revision of S3-212630 |
Huawei, HiSilicon, China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213124 | Conclusion on key issue #1.2 |
pCR revision of S3-212657 |
Huawei, HiSilicon, China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213125 | Conclusion on key issue #3.2 on protection of UE data in transit |
pCR revision of S3-212661 |
Huawei, HiSilicon, China Mobile | 33.866 0.5.0 | FS_eNA_SEC | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213151 | Update_on_Key_issue#1.4 | pCR | Ericsson | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
withdrawn | [WTS] [JSN] |
S3-213152 | Update_on_Key_issue#1.4 |
pCR revision of S3-213015 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213153 | Update_on_Solution#12 |
pCR revision of S3-213017 |
Ericsson | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213154 | Update_on_Solution#5 |
pCR revision of S3-213016 |
Ericsson, Lenovo, Motorola Mobility | 33.866 0.6.0 | eNA | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
S3-213271 | Reply-LS on security aspects for the method of collection of data from the UE |
LS out LS is reply to S3-212427 LS To: SA WG2 revision of S3-212679 |
Guangdong OPPO Mobile Telecom. | Rel-17 |
S3-104-e AI: 5.16 |
approved | [WTS] [JSN] |
64 documents (0.33642315864563 seconds)