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-201506 | Reply LS on specification of NAS COUNT for 5G | LS in | C1-203971 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-201511 | LS on 5G SoR integrity protection mechanism |
LS in LS reply in S3-202251 |
C4-203367 |
S3-100-e AI: 4.1 |
replied to | [WTS] [JSN] | |||
S3-201512 | LS on Clarification on AAA-Server address |
LS in LS reply in S3-202048 |
C4-203452 |
S3-100-e AI: 4.1 |
postponed | [WTS] [JSN] | |||
S3-201513 | LS Reply on Multiple Kausf upon registering via multiple Serving Networks | LS in | C4-203568 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-201518 | Specification of NAS COUNT for 5G | LS in | GSMA FSAG |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-201534 | Reply LS on NSSAAF in slice specific authentication | LS in | S2-2004476 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-201558 | Resolution of editor's note in clause 6.3.2.1 | CR | NTT DOCOMO | 33.501 15.9.0 CR#857 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201559 | Resolution of editor's note in clause 6.3.2.1 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#858 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201560 | Discussion on treatment of editor's notes in 33.501 | discussion | NTT DOCOMO | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-201561 | resolution of editor's notes in clause 6.8.1.2.0 | CR | NTT DOCOMO | 33.501 15.9.0 CR#859 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201562 | resolution of editor's notes in clause 6.8.1.2.0 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#860 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201563 | resolution of editor's note in clause 6.8.1.2.2 | CR | NTT DOCOMO | 33.501 15.9.0 CR#861 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201564 | resolution of editor's note in clause 6.8.1.2.2 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#862 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201565 | resolution of editor's note in clause 6.8.1.2.4 | CR | NTT DOCOMO, ZTE | 33.501 15.9.0 CR#863 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201566 | resolution of editor's note in clause 6.8.1.2.4 - R16 mirror | CR | NTT DOCOMO, ZTE | 33.501 16.3.0 CR#864 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201567 | resolution of editor's note in clause 6.9.1 | CR | NTT DOCOMO | 33.501 15.9.0 CR#865 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201568 | resolution of editor's note in clause 6.9.1 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#866 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201569 | resolution of editor's note in clause 6.9.4.1 | CR | NTT DOCOMO | 33.501 15.9.0 CR#867 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201570 | resolution of editor's note in clause 6.9.4.1 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#868 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201571 | resolution of editor's note in clause 6.9.4.2 | CR | NTT DOCOMO | 33.501 15.9.0 CR#869 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201572 | resolution of editor's note in clause 6.9.4.2 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#870 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201573 | resolution of editor's note in clause 6.9.4.3 | CR | NTT DOCOMO | 33.501 15.9.0 CR#871 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201574 | resolution of editor's note in clause 6.9.4.3 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#872 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201575 | resolution of editor's note in clause 10.2.2.2 |
CR revised to S3-202193 |
NTT DOCOMO | 33.501 15.9.0 CR#873 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201576 | resolution of editor's note in clause 10.2.2.2 - R16 mirror |
CR revised to S3-202196 |
NTT DOCOMO | 33.501 16.3.0 CR#874 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201577 | resolution of editor's note in clause 13.2.4.4.1 | CR | NTT DOCOMO | 33.501 15.9.0 CR#875 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201578 | resolution of editor's note in clause 13.2.4.4.1 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#876 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201579 | resolution of editor's note in clause 13.5 | CR | NTT DOCOMO | 33.501 15.9.0 CR#877 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201580 | resolution of editor's note in clause 13.5 - R16 mirror | CR | NTT DOCOMO | 33.501 16.3.0 CR#878 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201646 | Discussion paper on contradictory text on Kseaf deletion | discussion | Nokia, Nokia Shanghai Bell |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-201649 | CR on Kseaf text deletion |
CR revised to S3-202199 |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.501 16.3.0 CR#883 catF | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201651 | CR on Kseaf text deletion |
CR revised to S3-202200 |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.501 15.9.0 CR#884 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201653 | Discussion paper on Profile B uncompressed mode misalignment with CT6 | discussion | Nokia, Nokia Shanghai Bell | Rel-16 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | ||
S3-201655 | CR to delete uncompressed mode text in profile B |
CR revised to S3-202201 |
Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#885 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201656 | CR to delete uncompressed mode text in Profile B | CR | Nokia, Nokia Shanghai Bell | 33.501 15.9.0 CR#886 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201657 | Draft LS to CT6 on Profile B uncompressed mode |
LS out LS To: CT6 |
Nokia, Nokia Shanghai Bell |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-201678 | Edirorials on 13.4.1.2 Service access authorization in roaming scenarios-R15 | CR | ZTE Corporation | 33.501 15.9.0 CR#887 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201679 | Edirorials on 13.4.1.2 Service access authorization in roaming scenarios-R16 |
CR revised to S3-202243 |
ZTE Corporation | 33.501 16.3.0 CR#888 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201731 | Alignment with RAN3 specification in R16 | CR | Huawei, Hisilicon | 33.501 16.3.0 CR#889 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201732 | Alignment with RAN3 specification in R15 | CR | Huawei, Hisilicon | 33.501 15.9.0 CR#890 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201733 | SUPI Type Clarification in R16 |
CR revised to S3-202236 |
Huawei, Hisilicon | 33.501 16.3.0 CR#891 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201734 | SUPI Type Clarification in R15 |
CR revised to S3-202237 |
Huawei, Hisilicon | 33.501 15.9.0 CR#892 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201743 | AMF selection in NSSAA related procedure in case of dual registration in different PLMNs | discussion | Huawei, Hisilicon | eNS | Rel-16 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-201744 | AMF selection in NSSAA related procedure in case of dual registration in different PLMNs | CR | Huawei, Hisilicon | 33.501 16.3.0 CR#893 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201745 | Slice privacy protection in NSSAA related procedure | CR | Huawei, Hisilicon | 33.501 16.3.0 CR#894 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201746 | Correction to Nnssaaf_NSSAA services service |
CR revised to S3-202239, S3-202240 |
Huawei, Hisilicon | 33.501 16.3.0 CR#895 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201747 | Secondary authentication revocation |
CR revised to S3-202241 |
Huawei, Hisilicon | 33.501 15.9.0 CR#896 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201748 | Secondary authentication revocation |
CR revised to S3-202242 |
Huawei, Hisilicon | 33.501 16.3.0 CR#897 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201781 | Addressing editor note on transformation of S-NSSAI during NSSAA | CR | China Mobile | 33.501 16.3.0 CR#898 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201805 | Modification on AAA Server triggered Slice-Specific Authorization Revocation procedure |
CR revised to S3-202245 |
CATT | 33.501 16.3.0 CR#909 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201812 | Discussion on validity period | discussion | Huawei, HiSilicon | FS_eNS_SEC | Rel-16 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-201813 | validity peirod of NSSAA results | CR | Huawei, HiSilicon | 33.501 16.3.0 CR#910 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201814 | Discussion on SN-ID in NSSAA | discussion | Huawei, HiSilicon | eNS | Rel-16 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-201815 | Serving network name in NSSAA | CR | Huawei, HiSilicon | 33.501 16.3.0 CR#911 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201816 | Clarification on binding of NSSAI and UE ID at AAA-S | CR | Huawei, HiSilicon | 33.501 16.3.0 CR#912 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201817 | Editorial changes to clause 16 |
CR revised to S3-202231 |
Huawei, HiSilicon | 33.501 16.3.0 CR#913 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201841 | Change the long-lived TLS connection of N32-C to the short-lived |
CR revised to S3-202208 |
Huawei, Hisilicon | 33.501 15.9.0 CR#914 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201842 | Mirror: change the long-lived TLS connection of N32-C to the short-lived |
CR revised to S3-202209 |
Huawei, Hisilicon | 33.501 16.3.0 CR#915 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201843 | Update the N32-f context ID negotiation procedure |
CR revised to S3-202211 |
Huawei, Hisilicon | 33.501 15.9.0 CR#916 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201844 | Mirror: update the N32-f context ID negotiation procedure |
CR revised to S3-202222 |
Huawei, Hisilicon | 33.501 16.3.0 CR#917 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201848 | Discussion on the N32-f Protection Policy IE Data-Type Mapping issue | discussion | Huawei, Hisilicon | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-201849 | Reply LS on N32-f Protection Policy IE Data-Type Mapping |
LS out LS To: 5GIS, CT4 revised to S3-202224 |
Huawei, Hisilicon | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] | |
S3-201867 | Clarification of direct NAS reroute |
CR revised to S3-202206 |
Huawei, Hisilicon | 33.501 15.9.0 CR#920 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201868 | Mirror:Clarification of direct NAS reroute |
CR revised to S3-202207 |
Huawei, Hisilicon | 33.501 16.3.0 CR#921 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201889 | Correction to SN Addition or modification |
CR revised to S3-202175 |
Lenovo, Motorola Mobility | 33.501 16.3.0 CR#924 catF | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-201914 | Correction of the full form of the abbreviation NRF | CR | Ericsson | 33.501 15.9.0 CR#925 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201915 | Correction of the full form of the abbreviation NRF | CR | Ericsson | 33.501 16.3.0 CR#926 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-201916 | Verification of Serving Network Name in AUSF | discussion | Ericsson |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-201917 | Verification of Serving Network Name in AUSF | CR | Ericsson | 33.501 15.9.0 CR#927 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201918 | Verification of Serving Network Name in AUSF | CR | Ericsson | 33.501 16.3.0 CR#928 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-201919 | Aligning steering of roaming security mechanism with TS 29.509, TS 29.503 and TS 24.501 | CR | Ericsson | 33.501 15.9.0 CR#929 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
merged | [WTS] [JSN] |
S3-201920 | Aligning steering of roaming security mechanism with TS 29.509, TS 29.503 and TS 24.501 | CR | Ericsson | 33.501 16.3.0 CR#930 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
merged | [WTS] [JSN] |
S3-201921 | Draft LS on Misalignment between TS 33.501 and TS 29.573 (N32-f, references to the encrypted values) |
LS out LS To: CT4 |
Ericsson, NCSC | Rel-15 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | ||
S3-201922 | Aligning TS 33.501 with TS 29.573 regarding N32-f context ID | CR | Ericsson | 33.501 15.9.0 CR#931 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
merged | [WTS] [JSN] |
S3-201923 | Aligning TS 33.501 with TS 29.573 regarding N32-f context ID | CR | Ericsson | 33.501 16.3.0 CR#932 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
merged | [WTS] [JSN] |
S3-201954 | Reply LS on 5G SoR integrity protection mechanism |
LS out LS is reply to S3-201511 LS To: CT4 |
Qualcomm Incorporated |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-201975 | Alignment of SoR procedures to Stage-3 | CR | Samsung | 33.501 15.9.0 CR#935 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
merged | [WTS] [JSN] |
S3-201976 | Alignment of SoR procedures to Stage-3 | CR | Samsung | 33.501 16.3.0 CR#936 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
merged | [WTS] [JSN] |
S3-202048 | Draft LS Response on Clarification on AAA-Server address |
LS out LS is reply to S3-201512 source LS: C4-203452 LS To: CT4, SA2 |
Ericsson | Rel-16 |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | ||
S3-202049 | Clarifications to SoR integrity protection mechanism |
CR revised to S3-202248 |
Orange | 33.501 15.9.0 CR#943 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-202050 | Clarifications to SoR integrity protection mechanism |
CR revised to S3-202249 |
Orange | 33.501 16.3.0 CR#944 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-202055 | N32-f Protection Policy IE Data-Type Mapping |
LS in LS reply in S3-202224 |
GSMA |
S3-100-e AI: 4.1 |
replied to | [WTS] [JSN] | |||
S3-202056 | N32-f Error Responses - Mapping | LS in | GSMA |
S3-100-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-202160 | LS on Misalignments on HTTP message format over N32-f | LS in | C4-204409 |
S3-100-e AI: 4.1 |
postponed | [WTS] [JSN] | |||
S3-202164 | Error handling by the receiving NF | CR | Nokia, Nokia Shanghai Bell | 33.501 15.9.0 CR#946 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202165 | Error handling by the receiving NF | CR | Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#947 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202175 | Correction to SN Addition or modification |
CR revision of S3-201889 |
Lenovo, Motorola Mobility | 33.501 16.3.0 CR#9241 catF | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202193 | resolution of editor's note in clause 10.2.2.2 |
CR revision of S3-201575 |
NTT DOCOMO | 33.501 15.9.0 CR#8731 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202194 | NF Service Producer authorization | CR | Nokia, Nokia Shanghai Bell | 33.501 15.9.0 CR#950 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202195 | NF Service Producer authorization | CR | Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#951 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202196 | resolution of editor's note in clause 10.2.2.2 - R16 mirror |
CR revision of S3-201576 |
NTT DOCOMO | 33.501 16.3.0 CR#8741 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202197 | OAuth 2.0 based authorization | CR | Nokia, Nokia Shanghai Bell | 33.501 15.9.0 CR#952 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-202198 | OAuth 2.0 based authorization | CR | Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#953 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-202199 | CR on Kseaf text deletion |
CR revision of S3-201649 |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.501 16.3.0 CR#8831 catF | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202200 | CR on Kseaf text deletion |
CR revision of S3-201651 |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.501 15.9.0 CR#8841 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202201 | CR to delete uncompressed mode text in profile B |
CR revision of S3-201655 |
Nokia, Nokia Shanghai Bell, Verizon | 33.501 16.3.0 CR#8851 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202206 | Clarification of direct NAS reroute |
CR revision of S3-201867 |
Huawei, Hisilicon | 33.501 15.9.0 CR#9201 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202207 | Mirror:Clarification of direct NAS reroute |
CR revision of S3-201868 |
Huawei, Hisilicon | 33.501 16.3.0 CR#9211 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202208 | Change the long-lived TLS connection of N32-C to the short-lived |
CR revision of S3-201841 |
Huawei, Hisilicon, Nokia, Nokia Shanghai Bell | 33.501 15.9.0 CR#9141 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202209 | Mirror: change the long-lived TLS connection of N32-C to the short-lived |
CR revision of S3-201842 |
Huawei, Hisilicon, Nokia, Nokia Shanghai Bell | 33.501 16.3.0 CR#9151 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202211 | Update the N32-f context ID negotiation procedure |
CR revision of S3-201843 |
Huawei, Hisilicon, Ericsson | 33.501 15.9.0 CR#9161 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202222 | Mirror: update the N32-f context ID negotiation procedure |
CR revision of S3-201844 |
Huawei, Hisilicon, Ericsson | 33.501 16.3.0 CR#9171 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202224 | Reply LS on N32-f Protection Policy IE Data-Type Mapping |
LS out LS To: GSMA FASG 5GIS, CT4 revision of S3-201849 |
Huawei, Hisilicon | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
approved | [WTS] [JSN] | |
S3-202231 | Corrections to clause 16 |
CR revision of S3-201817 |
Huawei, HiSilicon | 33.501 16.3.0 CR#9131 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202236 | SUPI Type Clarification in R16 |
CR revision of S3-201733 |
Huawei, Hisilicon | 33.501 16.3.0 CR#8911 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-202237 | SUPI Type Clarification in R15 |
CR revision of S3-201734 |
Huawei, Hisilicon | 33.501 15.9.0 CR#8921 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-202239 | Correction to Nnssaaf_NSSAA services service |
CR revision of S3-201746 |
Huawei, Hisilicon | 33.501 16.3.0 CR#8951 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-202240 | Correction to Nnssaaf_NSSAA services service |
CR revision of S3-201746 |
Huawei, Hisilicon | 33.501 16.3.0 CR#8952 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
withdrawn | [WTS] [JSN] |
S3-202241 | Secondary authentication revocation |
CR revision of S3-201747 |
Huawei, Hisilicon | 33.501 15.9.0 CR#8961 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-202242 | Secondary authentication revocation |
CR revision of S3-201748 |
Huawei, Hisilicon | 33.501 16.3.0 CR#8971 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-202243 | Edirorials on 13.4.1.2 Service access authorization in roaming scenarios-R16 |
CR revision of S3-201679 |
ZTE Corporation | 33.501 16.3.0 CR#8881 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202245 | Modification on AAA Server triggered Slice-Specific Authorization Revocation procedure |
CR revision of S3-201805 |
CATT | 33.501 16.3.0 CR#9091 catF | eNS | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202248 | Clarifications to SoR integrity protection mechanism |
CR revision of S3-202049 |
Orange, Ericsson, Samsung | 33.501 15.9.0 CR#9431 catF | 5GS_Ph1-SEC | Rel-15 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202249 | Clarifications to SoR integrity protection mechanism |
CR revision of S3-202050 |
Orange, Ericsson, Samsung | 33.501 16.3.0 CR#9441 catA | 5GS_Ph1-SEC | Rel-16 |
S3-100-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-202251 | Reply LS on LS on 5G SoR integrity protection mechanism |
LS out LS is reply to S3-201511 LS To: CT4 |
Orange | Rel-16 |
S3-100-e AI: 4.1 |
approved | [WTS] [JSN] |
115 documents (0.33186888694763 seconds)