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-244605 | Discussion paper for CT1 LS on expected UE behavior on potential SUCI computation failure | discussion | Deutsche Telekom AG | TEI19 | Rel-19 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-244607 | TCG progress - report from TCG rapporteur | report | InterDigital Belgium. LLC |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244627 | LS to 3GPP CT4 on recursively defined JSON structures and reply to LS C4-241343 | LS in | GSMA |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244628 | LS on including the HPLMN ID in the PC5 discovery messages for 5G ProSe UE-to-UE relay |
LS in LS reply in S3-244961, S3-245128, S3-245136 |
C1-244647 |
S3-119 AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-244629 | LS on UE behaviour in case of SUCI calculation failure |
LS in LS reply in S3-245137, S3-244729, S3-245137 |
C1-245039 |
S3-119 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-244630 | Reply LS on Mitigation of Downgrade attacks | LS in | C1-245048 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244631 | Reply-LS on GSMA CVD-2023-0069 5G Core Network Attacks |
LS in LS reply in S3-244845, S3-244845 |
C4-243671 |
S3-119 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-244632 | Reply LS on clarification on home network triggered re-authentication |
LS in LS reply in S3-244973 |
C4-244496 |
S3-119 AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-244633 | LS on use of 3gpp-Sbi-Originating-Network-Id for Indirect Network Sharing case |
LS in LS reply in S3-244727, S3-244751 |
C4-244497 |
S3-119 AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-244634 | LS on PWS support for NB-IoT NTN | LS in | R2-2409243 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244635 | Response LS on Newly published data channel GSMA PRD TS.66 | LS in | R5-245464 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244636 | LS on AIML data collection |
LS in LS reply in S3-245138, S3-244713, S3-244728, S3-244948, S3-245038, S3-245138 |
RP-242389 |
S3-119 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-244637 | LS on Completion of 5WWC_Ph2 (R18) work | LS in | S2-2409022 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244638 | LS Reply to Issues related to Analytics context transfer between AnLF(s) |
LS in LS reply in S3-244875, S3-244990, S3-245055 |
S2-2409441 |
S3-119 AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-244639 | Reply LS on LCS user plane connection binding to the UE | LS in | S2-2409544 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244640 | Further LS Reply on Internal 5G Core information expose to trusted AF | LS in | S2-2410813 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244641 | LS on security aspects of Ambient IoT |
LS in LS reply in S3-244800, S3-244863, S3-244925, S3-244944, S3-244958, S3-245012, S3-245139 |
S2-2411049 |
S3-119 AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-244642 | Reply LS on AIML data collection | LS in | S2-2411191 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244643 | Reply LS on Clarification regarding definition of 5G NR femto ownership | LS in | S2-2411241 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244644 | Reply to Reply LS on CEN's requirements for eCall over IMS | LS in | S2-2411246 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244646 | LS on enhancement to the protocol stack of IMS Data Channel |
LS in LS reply in S3-245140, S3-245074, S3-245140 |
S4-241373 |
S3-119 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-244647 | LS Reply on Newly Published data channel GSMA PRD TS.66 | LS in | S4-241684 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244648 | LS reply to IETF Traffic Engineering Architecture and Signaling Working Group on ""A Realization of Network Slices for 5G Networks Using Current IP/MPLS Technologies"" | LS in | S5-244662 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244649 | LS Reply on Internal 5G Core information expose to trusted AF | LS in | S5-245162 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244650 | LS on SA5 MonStra work progress | LS in | S5-246296 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244651 | LS on Clarification related to Internal 5G Core information expose to trusted AF |
LS in LS reply in S3-245141, S3-244844, S3-245141 |
S6-242714 |
S3-119 AI: 3.1 |
replied to | [WTS] [JSN] | |||
| S3-244652 | LS on SA6 Answer to GSMA LS on Newly published data channel GSMA PRD TS.66 | LS in | S6-243763 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244653 | Reply LS on Newly published data channel GSMA PRD TS.66 | LS in | SP-241404 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244654 | Reply LS on AIML Data Collection | LS in | S5-246299 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244697 | Discussion paper on SUCI calculation | discussion | Nokia | Rel-19 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-244707 | Reply LS to CT4 on use of 3gpp-Sbi-Originating-Network-Id for Indirect Network Sharing case |
LS out LS is reply to S3-244633 source LS: C4-244497 LS To: CT4 |
Nokia | Rel-19 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-244708 | New (mini) WID on SUCI calculation failure alignment | WID new | Nokia | Rel-19 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-244711 | Discussion paper on SUCI calculation failure | discussion | Apple |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244712 | Reply LS to CT1 on UE bahaviour in case of SUCI calculation failure |
LS out LS To: CT1 |
Apple |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |||
| S3-244713 | Reply LS on AIML data collection |
LS out LS is reply to S3-244636 LS To: RAN |
Apple |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |||
| S3-244726 | Discussion on PLMN ID setting in the 3gpp-Sbi-Originating-Network-Id header in the Indirect Network Sharing case during UE authentication | discussion | China Unicom, ZTE Corporation |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244727 | Reply LS to CT4 on use of 3gpp-Sbi-Originating-Network-Id for Indirect Network Sharing case |
LS out LS is reply to S3-244633 LS To: CT4 |
China Unicom |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244728 | Reply LS on AIML data collection |
LS out LS is reply to S3-244636 LS To: RAN, RAN2, SA2 |
vivo | NR_AIML_air | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-244729 | Reply LS on UE behaviour in case of SUCI calculation failure |
LS out LS is reply to S3-244629 LS To: CT1 |
vivo | 5GProtoc19 | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-244730 | UE behaviour in case of SUCI calculation failure | CR | vivo | 33.501 19.0.0 CR#2066 catF | TEI19 | Rel-19 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-244748 | draft - Reply LS on clarification on home network triggered re-authentication |
LS out LS To: CT4 |
ZTE Corporation | Rel-18 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-244749 | Clarifications for HONTRA procedure with respect to failure cases | CR | ZTE | 33.501 18.7.0 CR#2067 catF | HN_Auth | Rel-18 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-244750 | Clarifications for HONTRA procedure with respect to failure cases | CR | ZTE | 33.501 19.0.0 CR#2068 catA | HN_Auth | Rel-19 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-244751 | reply LS to CT4 on use of 3gpp-Sbi-Originating-Network-Id for Indirect Network Sharing case |
LS out LS is reply to S3-244633 LS To: CT4 |
ZTE Corporation |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244752 | Security aspects for Indirect Network Sharing | CR | ZTE Corporation | 33.501 19.0.0 CR#2069 catF | TEI19 | Rel-19 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-244800 | Reply LS on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 LS To: SA2 revised to S3-245139 |
OPPO | Rel-19 |
S3-119 AI: 3.1 |
revised | [WTS] [JSN] | ||
| S3-244803 | KI#3 Discussion related to SA2 LS S2-2411049 | discussion | Sony | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-244805 | [draft] Reply LS to SA2 on on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 source LS: S2-2411049 LS To: SA2 |
Sony | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-244844 | draft reply LS to SA6 Internal 5G Core information expose to trusted AF |
LS out LS is reply to S3-244651 LS To: SA6 revised to S3-245141 |
Huawei, HiSilicon | Rel-18 |
S3-119 AI: 3.1 |
revised | [WTS] [JSN] | ||
| S3-244845 | Reply LS to CT4 on GSMA CVD-2023-0069 5G Core Network Attacks |
LS out LS is reply to S3-244631 LS To: CT4 |
Huawei, HiSilicon | Rel-18 |
S3-119 AI: 3.1 |
approved | [WTS] [JSN] | ||
| S3-244850 | RCS lawful intercept requirements | LS in | s3i240708 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244851 | Reply LS on UE-Satellite-UE Communication Architectures | LS in | s3i240752 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244854 | LS on request for IMS Data Channel related clarifications | LS in | s3i240707 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244855 | Reply LS on enhancement to the protocol stack of IMS Data Channel |
LS out LS is reply to S3-244646 LS To: SA4 revised to S3-245140 |
China Mobile | Rel-18 |
S3-119 AI: 3.1 |
revised | [WTS] [JSN] | ||
| S3-244861 | Discission paper concerning RAN agreements | discussion | Nokia |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244863 | LS reply to LS on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 source LS: S3-244641 LS To: SA2 |
Nokia |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |||
| S3-244864 | LS reply to LS on RAN2 agreements and assumptions for Ambient IoT |
LS out source LS: S3-242753 LS To: RAN2 |
Nokia |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244875 | Reply LS on Issues related to Analytics context transfer between AnLF(s) |
LS out LS is reply to S3-244638 source LS: S2-2409441 LS To: SA2 |
Huawei, HiSilicon | eNA_Ph3_SEC | Rel-18 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-244897 | Discussion paper on SUCI error handling | discussion | Huawei, HiSilicon | Rel-19 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-244925 | reply LS on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 source LS: S2-2411049 LS To: SA2 |
Huawei, HiSilicon | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-244944 | Reply LS on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 LS To: SA2 |
China Mobile | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-244947 | Discussion on RAN plenary LS on AIML | discussion | Qualcomm Incorporated |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244948 | Reply LS on AIML data collection |
LS out LS is reply to S3-244636 LS To: RAN |
Qualcomm Incorporated |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |||
| S3-244949 | Discussion on incoming SUCI LS | discussion | Qualcomm Incorporated |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-244950 | Reply LS on UE behaviour in case of SUCI calculation failure |
LS out LS is reply to C1-245039 LS To: CT1 revised to S3-245137 |
Qualcomm Incorporated | 5GProtoc19 | Rel-19 |
S3-119 AI: 3.1 |
revised | [WTS] [JSN] | |
| S3-244958 | reply LS on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 LS To: SA2 |
Qualcomm Incorporated | FS_AmbientIoT | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-244961 | reply LS on including the HPLMN ID in the PC5 discovery messages for 5G ProSe UE-to-UE relay |
LS out LS is reply to S3-244628 LS To: CT1 |
Qualcomm Incorporated | 5G_ProSe_Ph2 | Rel-18 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-244967 | [Draft] Reply LS on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 source LS: S2-2411049 LS To: SA2 |
Beijing Xiaomi Mobile Software | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | ||
| S3-244973 | [Draft] Reply LS on clarification on home network triggered re-authentication |
LS out LS is reply to S3-244632 source LS: C4-244496 LS To: CT4 |
Beijing Xiaomi Mobile Software | Rel-18 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-244974 | Clarification for re-authentication notification response in HONTRA procedure | CR | Xiaomi | 33.501 18.7.0 CR#2078 catF | HN_Auth | Rel-18 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-244975 | Clarification for re-authentication notification response in HONTRA procedure | CR | Xiaomi | 33.501 19.0.0 CR#2079 catA | HN_Auth | Rel-19 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-244990 | Reply LS on Issues related to Analytics context transfer between AnLF(s) |
LS out LS is reply to S3-244638 LS To: SA2 |
CATT | Rel-18 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-245012 | Draft_LS reply to LS on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 LS To: SA2 |
Ericsson | FS_Ambient_IoT_Sec | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | |
| S3-245038 | [draft] Reply LS on AIML data collection |
LS out LS is reply to S3-244636 source LS: RP-242389 LS To: RAN revised to S3-245138 |
Samsung | Rel-19 |
S3-119 AI: 3.1 |
revised | [WTS] [JSN] | ||
| S3-245045 | Discussion paper on SUCI calculation failure | discussion | Samsung | Rel-19 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-245046 | [draft] Reply LS on UE behaviour in case of SUCI calculation failure |
LS out LS is reply to S3-244629 source LS: C1-245039 LS To: CT1 |
Samsung | Rel-19 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | ||
| S3-245055 | LS reply on Issues related to Analytics context transfer between AnLF(s) |
LS out LS is reply to S3-244638 LS To: SA2 |
Ericsson | Rel-18 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-245073 | IMS Data Channel and LI | discussion | Ericsson | Rel-18 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-245074 | [Draft] Reply LS on enhancement to the protocol stack of IMS Data Channel |
LS out LS is reply to S3-244646 LS To: SA4 |
Ericsson | Rel-18 |
S3-119 AI: 3.1 |
merged | [WTS] [JSN] | ||
| S3-245075 | HONTRA Error Handling | CR | Ericsson | 33.501 18.7.0 CR#2084 catF | HN_Auth | Rel-18 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-245076 | HONTRA Error Handling | CR | Ericsson | 33.501 19.0.0 CR#2085 catA | HN_Auth | Rel-19 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-245077 | [Draft] Reply LS on clarification on home network triggered re-authentication |
LS out LS To: CT4 |
Ericsson | HN_Auth | Rel-18 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-245127 | Support cleartext HPLMN ID in PC5 U2U relay discovery | CR | Nokia, Nokia Shanghai Bell | 33.503 18.4.0 CR#210 catF | 5G_ProSe_Ph2 | Rel-18 |
S3-119 AI: 3.1 |
not pursued | [WTS] [JSN] |
| S3-245128 | Reply LS on including HPLMN ID in the PC5 discovery messages for 5G ProSe UE-to-UE relay |
LS out LS is reply to S3-244628 source LS: C1-244647 LS To: CT1 revised to S3-245136 |
Nokia, Nokia Shanghai Bell | 5G_ProSe_Ph2 | Rel-18 |
S3-119 AI: 3.1 |
revised | [WTS] [JSN] | |
| S3-245133 | LS on draft-ietf-raw-technologies, "Reliable and Available Wireless Technologies | LS in | IETF |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-245136 | Reply LS on including HPLMN ID in the PC5 discovery messages for 5G ProSe UE-to-UE relay |
LS out LS is reply to S3-244628 source LS: C1-244647 LS To: CT1 revision of S3-245128 |
Nokia, Nokia Shanghai Bell | 5G_ProSe_Ph2 | Rel-18 |
S3-119 AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-245137 | Reply LS on UE behaviour in case of SUCI calculation failure |
LS out LS is reply to S3-244629 LS To: CT1,Ct6 LS reply in C6-240721 revision of S3-244950 |
Qualcomm Incorporated | 5GProtoc19 | Rel-19 |
S3-119 AI: 3.1 |
approved | [WTS] [JSN] | |
| S3-245138 | Reply LS on AIML data collection |
LS out LS is reply to S3-244636 source LS: RP-242389 LS To: RAN revision of S3-245038 |
Samsung | Rel-19 |
S3-119 AI: 3.1 |
approved | [WTS] [JSN] | ||
| S3-245139 | LS on security aspects of Ambient IoT |
LS out LS is reply to S3-244641 LS To: SA2 revision of S3-244800 |
OPPO | Rel-19 |
S3-119 AI: 3.1 |
approved | [WTS] [JSN] | ||
| S3-245140 | Reply LS on enhancement to the protocol stack of IMS Data Channel |
LS out LS is reply to S3-244646 LS To: SA4 revision of S3-244855 |
China Mobile | Rel-18 |
S3-119 AI: 3.1 |
approved | [WTS] [JSN] | ||
| S3-245141 | Reply LS to SA6 Internal 5G Core information expose to trusted AF |
LS out LS is reply to S3-244651 LS To: SA6 revision of S3-244844 |
Huawei, HiSilicon | Rel-18 |
S3-119 AI: 3.1 |
approved | [WTS] [JSN] | ||
| S3-250004 | LS on security aspects of Ambient IoT | LS in | S2-2411049 |
S3-119-e AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-250005 | LS on RAN2 outcome of Ambient IoT study | LS in | R2-2411263 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250006 | Reply to LS on Further Clarification for Ambient IoT Security | LS in | S1-244920 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250007 | LS on A-IoT Conclusions in SA WG2 | LS in | S2-2413035 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250008 | Reply LS on terminology alignment between SA6 and SA3 | LS in | S6-245644 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250009 | Reply LS on clarifications on consent management | LS in | SP-241934 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250043 | Reply LS on security aspects of Ambient IoT |
LS out LS is reply to S3-250004/S2-2411049 LS To: SA2 |
OPPO | Rel-19 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250071 | LS reply to LS on security aspects of Ambient IoT |
LS out source LS: S3-244641 LS To: SA2 |
Nokia | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-250130 | LS on User Consent aspects for Energy Saving |
LS out LS To: SA WG2 |
Ericsson | Rel-19 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250237 | SA3 Leadership meeting notes | report | MCC |
S3-119-e AI: 3.1 |
available | [WTS] [JSN] |
101 documents (0.35633301734924 seconds)