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-260100 | Agenda |
agenda revised to S3-260162 |
SA WG3 Chair |
S3-126 AI: 1 |
revised | [WTS] [JSN] | |||
| S3-260101 | Report from SA3#125 | report | MCC |
S3-126 AI: 2.1 |
approved | [WTS] [JSN] | |||
| S3-260102 | Report from SA3#125-Adhoc-e | report | MCC |
S3-126 AI: 2.1 |
approved | [WTS] [JSN] | |||
| S3-260103 | Process for SA3#126 | other | SA WG3 Chair |
S3-126 AI: 1 |
noted | [WTS] [JSN] | |||
| S3-260104 | Detailed agenda planning | other | SA WG3 Chair |
S3-126 AI: 1 |
noted | [WTS] [JSN] | |||
| S3-260105 | Report from last SA | report | SA WG3 Chair |
S3-126 AI: 2.1 |
noted | [WTS] [JSN] | |||
| S3-260106 | Reply LS on Structure updates of AIoT Identifiers |
LS in source LS: C4-255349 LS To: SA2, RAN2, RAN3 |
CT4 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260107 | Reply LS on AIoT Device Permanent ID Length |
LS in source LS: C4-255403 LS To: SA2 |
CT4 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260108 | Out of sync t-ID handling for AIoT |
LS in source LS: C4-255429 LS To: SA3 LS reply in S3-260871 |
CT4 |
S3-126 AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-260109 | LS on User consent for Data collection at the UE for NW-side model training |
LS in source LS: R2-2506541 LS To: SA3 |
RAN2 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260110 | LS on Security parameter in A-IoT paging |
LS in source LS: R2-2507920 LS To: SA3 |
RAN2 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260111 | LS on Voice over NB-IoT NTN |
LS in source LS: R2-2509213 LS To: RAN, SA2, SA3, CT1 |
RAN2 |
S3-126 AI: 3 |
withdrawn | [WTS] [JSN] | |||
| S3-260112 | Reply LS on handling of service collision |
LS in source LS: R2-2509384 LS To: CT1 |
RAN2 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260113 | Reply LS to S2-2510958 = RP-253004 on AI/ML UE sided data collection (to: SA, SA2; cc: RAN2, SA3, SA5; contact: Interdigital) |
LS in source LS: RP-253847 LS To: SA, SA2 |
RAN |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260114 | Reply LS to SA3 on business model and architecture for SNPN cellular hotspots |
LS in source LS: S1-254498 LS To: SA3 |
SA1 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260115 | LS reply to SA2 (cc RAN2, SA4, CT1, SA3, RAN1) on IMS voice over NB-IoT NTN connected to EPC |
LS in source LS: S1-254508 LS To: SA2 |
SA1 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260116 | Reply LS to SA (cc SA2, SA3, SA4, SA6, CT) on external data channel content access requirements |
LS in source LS: S1-254509 LS To: SA |
SA1 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260117 | LS on AI/ML UE sided data collection |
LS in source LS: S2-2510958 LS To: RAN WG2, TSG RAN |
SA2 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260118 | Reply LS on Potential UDR in SNPN for AIoT |
LS in source LS: S2-2511008 LS To: SA WG3, CT WG4 |
SA2 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260119 | LS Response on IETF Network Slice Application in 3GPP 5G End-to-End Network Slice |
LS in source LS: S2-2511186 LS To: TSG SA |
SA2 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260120 | Reply LS on business model and architecture for SNPN cellular hotspots |
LS in source LS: S2-2511233 LS To: SA WG3 |
SA2 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260121 | LS on MANET multicast support for Layer-3 IP Type UE-to-UE multi-hop Relay |
LS in source LS: S2-2511306 LS To: RAN WG2, SA WG3 LS reply in S3-260772 |
SA2 |
S3-126 AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-260122 | Reply LS on LI requirements on IMS Data Channel |
LS in source LS: s3i250674 LS To: SA2, CT1, CT4 |
SA3-LI |
S3-126 AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-260123 | LS to SA2 on avatar Communications |
LS in source LS: S4-252113 LS To: SA WG2 |
SA4 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260124 | Reply LS to IETF_TEAS_LS_250917 = S5-255022 on IETF Network Slice Application in 3GPP 5G End-to-End Network Slice (to: SA; cc: SA2, SA3, RAN3; contact: Ericsson) |
LS in source LS: S5-255690 LS To: SA |
SA5 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260125 | Reply LS on external data channel content access |
LS in source LS: S6-255643 LS To: SA |
SA6 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260126 | LS to SA3 on FS_APCOT study |
LS in source LS: S6-255645 LS To: SA3 |
SA6 |
S3-126 AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-260127 | Reply LS on AI/ML UE sided data collection |
LS in source LS: SP-251687 LS To: TSG RAN, SA WG2, SA WG3, SA WG5 |
TSG SA |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260128 | Reply LS on Security parameter in A-IoT paging |
LS in source LS: SP-251691 LS To: RAN WG2, SA WG3 |
TSG SA |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260129 | LS Response on external data channel content access requirements |
LS in source LS: SP-251693 LS To: GSMA NG UPG |
TSG SA |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260130 | LS on Completion of AIML_CAL Study |
LS in source LS: SP-251699 LS To: TSG RAN, TSG CT, RAN1, RAN2, RAN3, RAN4, RAN5, CT1, CT3, CT4, CT6, SA1, SA2, SA3, SA4, SA5, SA6, SA3-LI |
TSG SA |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260131 | CVD-2025-0105 – GUTI Reuse in EPS Fallback vulnerability |
LS in source LS: CVD-2025-0105 LS To: 3GPP CT1, 3GPP SA3 |
GSMA CVD PoE |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260132 | Liaison_statement_to_3GPP_SA3_on_CRA_Open_consultation |
LS in source LS: CYBEREUSR(25)26b007r2 LS To: 3GPP SA3 |
ETSI TC CYBER WG EUSR |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260133 | Reply to LS on PQC transition for RFC 6509 |
LS in source LS: ls-secarea-reply-sa3-pqc-for-rfc-6509 LS To: SA3 |
IETF |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260134 | LS on initiation of a new work item related to coordination of networking and computing |
LS in source LS: SG17-LS75 LS To: SA3 |
ITU-T Study Group 17 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260135 | LS/r on informing about the latest PQTN TF publications (reply to GSMA_x0002_PQTN#93 Doc_003) |
LS in source LS: SG17-LS115 LS To: SA3 |
ITU-T Study Group 17 |
S3-126 AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-260136 | LS on DTLS for SCTP Progress Report | LS in | IETF |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260137 | Update to AMF SCAS according to NESASG feedback | draftCR | Nokia Korea | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260138 | Update to NRF SCAS according to NESASG feedback | draftCR | Nokia Korea | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260139 | Update to NWDAF SCAS according to NESASG feedback | draftCR | Nokia Korea | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260140 | Update to SEPP SCAS according to NESASG feedback | draftCR | Nokia Korea | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260141 | Update on Snow5G 256-bit Specification |
CR revised to S3-260156 |
Nokia Korea | 35.240 18.0.0 CR#1 catF | FS_256_Algo | Rel-20 |
S3-126 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-260142 | Update on Snow5G Implementation Test Data | CR | Nokia | 35.241 18.0.0 CR#1 catF | 256_Algo, TEI20 | Rel-20 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260143 | New KeyIssue in RAN security - SPARROW | pCR | Keysight Technologies UK Ltd | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260144 | Update on Snow5G Design Conformance Test Data | CR | Nokia | 35.242 18.0.0 CR#1 catF | 256_Algo, TEI20 | Rel-20 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260145 | Update on AES 256-bit Specification |
CR revised to S3-260804 |
Nokia | 35.243 18.0.0 CR#1 catF | 256_Algo | Rel-20 |
S3-126 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-260146 | Update on AES 256-bit Implementation Test Data | CR | Nokia | 35.244 18.0.0 CR#1 catF | 256_Algo, TEI20 | Rel-20 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260147 | Update on AES 256-bit Design Conformance Test Data | CR | Nokia | 35.245 18.0.0 CR#1 catF | 256_Algo, TEI20 | Rel-20 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260148 | Update on ZUC 256-bit Specification |
CR revised to S3-260805 |
Nokia | 35.246 19.0.0 CR#2 catF | 256_Algo | Rel-20 |
S3-126 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-260149 | Update on ZUC 256-bit Implementation Test Data | CR | Nokia | 35.247 18.0.0 CR#1 catF | 256_Algo, TEI20 | Rel-20 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260150 | Update on ZUC 256-bit Design Conformance Test Data |
CR revised to S3-260806 |
Nokia | 35.248 18.0.0 CR#1 catF | 256_Algo | Rel-20 |
S3-126 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-260151 | New KI on NF Authentication on Application Layer in 6G | pCR | Deutsche Telekom AG | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260152 | pCR on Terminology Update in Solution #8 | pCR | Deutsche Telekom AG | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260153 | Evaluation of SUCI Calculation Solutions and Recommendation for Solution #8 | discussion | Deutsche Telekom AG | Rel-20 |
S3-126 AI: 5.2.1 |
noted | [WTS] [JSN] | ||
| S3-260154 | pCR on conclusions for solutions for SUCI calculation | pCR | Deutsche Telekom AG | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
noted | [WTS] [JSN] |
| S3-260155 | TCG progress - report from TCG rapporteur | other | InterDigital, Inc. |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260156 | Update on Snow5G 256-bit Specification |
CR revision of S3-260141 revised to S3-260803 |
Nokia | 35.240 18.0.0 CR#11 catF | 256_Algo | Rel-20 |
S3-126 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-260157 | pCR to TS 33.502 – Detecting SBA layer parameters change |
pCR revised to S3-260778 |
Vodafone, Verizon, China Mobile, NTT DOCOMO, KDDI, AT&T, Deutsche Telekom, Telecom Italia | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-260158 | pCR to TS 33.502 – Removal of ENs |
pCR revised to S3-260780 |
Vodafone, Verizon, China Mobile, NTT DOCOMO, KDDI, AT&T, Deutsche Telekom, Telecom Italia | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-260159 | Corrections to "S3-260145: Update on AES 256-bit Specification" | draftCR | CHTTL | 256_Algo | Rel-20 |
S3-126 AI: 4.1.1 |
merged | [WTS] [JSN] | |
| S3-260160 | Corrections to "S3-260148: Update on ZUC 256-bit Specification" | draftCR | CHTTL | 256_Algo | Rel-20 |
S3-126 AI: 4.1.1 |
merged | [WTS] [JSN] | |
| S3-260161 | Corrections to "S3-260156: Update on Snow5G 256-bit Specification" | draftCR | CHTTL | 256_Algo | Rel-20 |
S3-126 AI: 4.1.1 |
merged | [WTS] [JSN] | |
| S3-260162 | Agenda |
agenda revision of S3-260100 |
SA WG3 Chair |
S3-126 AI: 1 |
approved | [WTS] [JSN] | |||
| S3-260163 | Discussion for SPARROW KeyIssue | discussion | Keysight Technologies UK Ltd | Rel-21 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] | ||
| S3-260164 | Considerations for TLS 1.3 |
pCR revised to S3-260898 |
AT&T Services, Inc. | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260165 | Update the clause 4 Architecture | pCR | Johns Hopkins University APL | 33.758 0.1.0 | FS_PLMNNPN_Ph2 | Rel-20 |
S3-126 AI: 5.2.4 |
approved | [WTS] [JSN] |
| S3-260166 | Update the clause 5 Security assumptions |
pCR revised to S3-260947 |
Johns Hopkins University APL | 33.758 0.1.0 | FS_PLMNNPN_Ph2 | Rel-20 |
S3-126 AI: 5.2.4 |
revised | [WTS] [JSN] |
| S3-260167 | Update the clause 6 evaluation for SBA interface protection | pCR | Johns Hopkins University APL | 33.758 0.1.0 | FS_PLMNNPN_Ph2 | Rel-20 |
S3-126 AI: 5.2.4 |
approved | [WTS] [JSN] |
| S3-260168 | Update the clause 7 Key issues | pCR | Johns Hopkins University APL | 33.758 0.1.0 | FS_PLMNNPN_Ph2 | Rel-20 |
S3-126 AI: 5.2.4 |
approved | [WTS] [JSN] |
| S3-260169 | Solving the Editors Notes in Solution 12 |
pCR revised to S3-260912 |
Nokia | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260170 | Solving the Editors Notes on the symmetric SUCI | pCR | Nokia | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260171 | PQC KEM solution for MIKEY-SAKKE | pCR | Nokia | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
noted | [WTS] [JSN] |
| S3-260172 | Proposed update for conclusion | pCR | Nokia | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
noted | [WTS] [JSN] |
| S3-260173 | Evaluation on the symmetric SUCI | pCR | Nokia | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260174 | Evaluation on the hybrid SUCI |
pCR revised to S3-260913 |
Nokia | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260175 | PQC DSA solution for MIKEY-SAKKE | pCR | Nokia | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
noted | [WTS] [JSN] |
| S3-260176 | Solving the Editors Notes Solution 2 |
pCR revised to S3-260903 |
Nokia | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260177 | Solution evaluation for solution 1 |
pCR revised to S3-260889 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260178 | Solution evaluation for solution 11 |
pCR revised to S3-261006 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260179 | Solution evaluation for solution 7 |
pCR revised to S3-260895 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260180 | Solution enhancements for solution 1 |
pCR revised to S3-260888 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260181 | Introduction of user scenarios for 256-bit support |
pCR revised to S3-260874 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260182 | Explanations of the Term AEAD | pCR | Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260183 | Updates on the terms related to AEAD | pCR | Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
merged | [WTS] [JSN] |
| S3-260184 | Draft TS 33.531 |
draft TS revised to S3-260278 |
Rakuten Mobile, Inc | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
revised | [WTS] [JSN] | |
| S3-260185 | pCR on SCAS for CAPIF Core Function section 4.2 | pCR | Rakuten Mobile, Inc | 33.531 0.1.0 | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
withdrawn | [WTS] [JSN] |
| S3-260186 | pCR on SCAS for CAPIF Core Function section 4.3.1 | pCR | Rakuten Mobile, Inc | 33.531 0.1.0 | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
withdrawn | [WTS] [JSN] |
| S3-260187 | pCR on SCAS for CAPIF Core Function test case | pCR | Rakuten Mobile, Inc | 33.531 0.1.0 | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
withdrawn | [WTS] [JSN] |
| S3-260188 | nested API invocation threat at CAPIF Core Function in TR 33.926 | CR | Rakuten Mobile, Inc | 33.926 19.4.0 CR#109 catB | SCAS_5GA_CAPIF | Rel-19 |
S3-126 AI: 5.1.7 |
withdrawn | [WTS] [JSN] |
| S3-260189 | Full Nonce Counter | discussion | Lenovo | Rel-19 |
S3-126 AI: 4.1.1 |
noted | [WTS] [JSN] | ||
| S3-260190 | Full nonce counter | CR | Lenovo | 33.501 19.5.0 CR#2204 catF | XRM_Ph2-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-260191 | Full Nonce Counter | CR | Lenovo | 33.501 20.0.0 CR#2205 catF | XRM_Ph2-SEC | Rel-20 |
S3-126 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-260192 | Support of AES-256 bit cryptography and other security enhancements in 5G-NTN | discussion | THALES, ESA, European Commission, Eutelsat, Hispasat, SES | Rel-20 |
S3-126 AI: 6.1 |
noted | [WTS] [JSN] | ||
| S3-260193 | Pseudo-CR on assumption update |
pCR revised to S3-260876 |
KDDI | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260194 | Pseudo-CR on Definitions and abbreviations | pCR | KDDI | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
merged | [WTS] [JSN] |
| S3-260195 | Pseudo-CR on new Key Issue Interworking and co-existence | pCR | KDDI | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260196 | Pseudo-CR on new solution for handling of input parameters for interworking | pCR | KDDI | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260197 | Pseudo-CR on Solution #2 update | pCR | KDDI | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260198 | Pseudo-CR on Solution #8 update | pCR | KDDI | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260199 | Reply LS on Out of sync T-ID handling for AIoT |
LS out LS is reply to S3-260108 LS To: CT4 |
vivo |
S3-126 AI: 3 |
merged | [WTS] [JSN] | |||
| S3-260200 | Correction on the use of Nadm_SecTID_Get | CR | vivo | 33.369 19.1.0 CR#71 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-260201 | Negotiation for privacy | CR | vivo | 33.369 19.1.0 CR#72 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-260202 | Add new terms and abbreviations | CR | vivo | 33.369 19.1.0 CR#73 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
withdrawn | [WTS] [JSN] |
| S3-260203 | Correction on clause 6.4.6-R15 | CR | vivo | 33.501 15.18.0 CR#2206 catF | 5GS_Ph1-SEC | Rel-15 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260204 | Correction on clause 6.4.6-R16 | CR | vivo | 33.501 16.18.0 CR#2207 catA | 5GS_Ph1-SEC | Rel-16 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260205 | Correction on clause 6.4.6-R17 | CR | vivo | 33.501 17.14.0 CR#2208 catA | 5GS_Ph1-SEC | Rel-17 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260206 | Correction on clause 6.4.6-R18 | CR | vivo | 33.501 18.10.0 CR#2209 catA | 5GS_Ph1-SEC | Rel-18 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260207 | Correction on clause 6.4.6-R19 | CR | vivo | 33.501 19.5.0 CR#2210 catA | 5GS_Ph1-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260208 | Correction on X.12.2 | CR | vivo | 33.501 19.5.0 CR#2211 catF | TEI19 | Rel-19 |
S3-126 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-260209 | Alignment based on AIML consistency alignment | CR | vivo | 33.501 19.5.0 CR#2212 catF | TEI19 | Rel-19 |
S3-126 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-260210 | Solution update on solution#14 |
pCR revised to S3-260915 |
vivo | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260211 | Clean Up for TR 33.785 |
pCR revised to S3-260774 |
vivo | 33.785 0.3.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-126 AI: 5.2.6 |
revised | [WTS] [JSN] |
| S3-260212 | Update conclusion on KI#1 | pCR | vivo | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260213 | SA#NEW Security and Privacy of Data Framework |
pCR revised to S3-260866 |
vivo, InterDigital, OPPO, China Mobile, Apple, CATT, Samsung, SKT | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260214 | SA#5 - KI#NEW - Vulnerability Resolution | pCR | vivo | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260215 | SA#5 - KI#NEW - Subscriber ID Protection | pCR | vivo | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260216 | Annex#NEW - Risk analysis of System Information and paging messages | pCR | vivo, SK telecom | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260217 | Align terms for AEAD | pCR | vivo | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
merged | [WTS] [JSN] |
| S3-260218 | Solution#4 Update on AEAD Algorithm Negotiation |
pCR revised to S3-260890 |
vivo | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260219 | New solutiion on AEAD Algorithm Interface |
pCR revised to S3-260881 |
vivo | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260220 | Update on A.3 Order of Operations |
pCR revised to S3-260875 |
vivo | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260221 | New Solution on Interoperability Analysis between AEAD-only and non-AEAD systems | pCR | vivo | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260222 | Corrections to the Nadm_SecTID_Get service operation and out of sync detection |
CR revised to S3-260870 |
Lenovo | 33.369 19.1.0 CR#74 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 3 |
revised | [WTS] [JSN] |
| S3-260223 | Pseudo-CR on 33.511 gNB SCAS - Key Refresh |
other revised to S3-260930 |
NPL | SCAS_5GA | Rel-19 |
S3-126 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-260224 | New T-ID Update Service Operation | CR | Lenovo | 33.369 19.1.0 CR#75 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-260225 | Correction of the Nadm_SecAuthentication_Get service operation |
CR revised to S3-260976 |
Lenovo | 33.369 19.1.0 CR#76 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-260226 | Removal of sending Device Permanent Identity | CR | Lenovo | 33.369 19.1.0 CR#77 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-260227 | Corrections in clause 5.2.2 Authentication procedure | CR | Lenovo | 33.369 19.1.0 CR#78 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
merged | [WTS] [JSN] |
| S3-260228 | pCR to TS 33.502 – Detecting events related to unexpected communication model flows |
pCR revised to S3-260779 |
Vodafone, Verizon, China Mobile, NTT DOCOMO, KDDI, AT&T, Deutsche Telekom, Telecom Italia | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-260229 | Presentation for Approval to TSG SA - Security related Events Handling |
TS or TR cover revised to S3-261009 |
Vodafone | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
revised | [WTS] [JSN] | |
| S3-260230 | New Key Issue on User Plane protocol security for RAN area | pCR | MITRE-FFRDC | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260231 | Update of Solution#15 with key identification | pCR | Lenovo | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260232 | Additional clarifications of Solution#15 | pCR | Lenovo | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260233 | Evaluation of Solution#15 | pCR | Lenovo | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260234 | MCX ETSI Plugtest Observations | discussion | Motorola Solutions UK Ltd. | MCXSec3 | Rel-18 |
S3-126 AI: 4.1.1 |
noted | [WTS] [JSN] | |
| S3-260235 | Pseudo-CR on MIKEY-SAKKE PQC evaluation |
pCR revised to S3-260720 |
Motorola Solutions UK Ltd. | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260236 | Reply to LS on Out of sync T-ID handling for AIoT |
LS out LS is reply to S3-260108 source LS: C4-255429 LS To: CT4 revised to S3-260871 |
Lenovo | Rel-19 |
S3-126 AI: 3 |
revised | [WTS] [JSN] | ||
| S3-260237 | SA#2 – KI#NEW - Security of RAN Control Plane Procedures | pCR | InterDigital, Inc. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260238 | SA#2 – KI#NEW - Security of RAN User Plane Procedures | pCR | InterDigital, Inc. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260239 | SA#2 – KI#NEW - System Information Security and Base Station Authenticity | pCR | InterDigital, Inc. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260240 | Updates to Solution#1 |
pCR revised to S3-260765 |
Lenovo, Motorola Mobility | 33.786 0.3.0 | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
revised | [WTS] [JSN] |
| S3-260241 | Updates to Solution#4 |
pCR revised to S3-260766 |
Lenovo, Motorola Mobility | 33.786 0.3.0 | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
revised | [WTS] [JSN] |
| S3-260242 | Conclusions to Key Issues | pCR | Lenovo, Motorola Mobility | 33.786 0.3.0 | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
merged | [WTS] [JSN] |
| S3-260243 | Editorial Clean-up for TR 33.786 | pCR | Lenovo, Motorola Mobility | 33.786 0.3.0 | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
approved | [WTS] [JSN] |
| S3-260244 | Discussion Paper to update the TR 33.786 Approval Timeline | discussion | Lenovo, Motorola Mobility | Rel-20 |
S3-126 AI: 6.3 |
noted | [WTS] [JSN] | ||
| S3-260245 | SA#2 – KI#NEW - Security of initial RAN messages prior to AS security activation |
pCR revised to S3-260809 |
InterDigital, Inc. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260246 | Revised SID on AIMLE Service Security | SID revised | Lenovo, Motorola Mobility | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 6.3 |
endorsed | [WTS] [JSN] | |
| S3-260247 | Replace Obsolete Version | pCR | Lenovo, Motorola Mobility | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
merged | [WTS] [JSN] |
| S3-260248 | Updates to Solution #16 | pCR | Lenovo, Motorola Mobility | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260249 | Solution for Hybrid PQC based SUCI Computation |
pCR revision of S3-254729 revised to S3-260807 |
Lenovo, Motorola Mobility | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260250 | SA#2 – KI#NEW - Security of Mobility and State Transitions in 6G | pCR | InterDigital, Inc. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260251 | SA#5 - KI#NEW - Authentication between UE and Network in 6GS | pCR | Lenovo, Motorola Mobility | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260252 | SA#5 - KI#NEW - Authentication for 3rd party service | pCR | Lenovo, Motorola Mobility | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260253 | SA#1 – KI#NEW - Security Domains and Trust Anchors |
pCR revised to S3-260868 |
InterDigital, Inc. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260254 | SA#1 – KI#NEW - 6G Key Hierarchy and Key Lifecycle Management |
pCR revised to S3-260869 |
InterDigital, Inc. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260255 | Conclusion for Key Issue #1 | pCR | InterDigital, Europe, Ltd., Nokia, Huawei, HiSilicon, Xiaomi, CableLabs, Charter Communications, Lenovo, Motorola Mobility | 33.778 0.2.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-126 AI: 5.2.5 |
noted | [WTS] [JSN] |
| S3-260256 | Add conclusions for Key Issues #1 and #2 |
pCR revised to S3-260773 |
InterDigital, Europe, Ltd. | 33.785 0.3.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-126 AI: 5.2.6 |
revised | [WTS] [JSN] |
| S3-260257 | Closing ENs for Solution #2 | pCR | InterDigital, Europe, Ltd. | 33.785 0.3.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-126 AI: 5.2.6 |
merged | [WTS] [JSN] |
| S3-260258 | pCR to TS 33.502 - Security related Events for unexpected SBI call flows | pCR | IIT Bombay | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
merged | [WTS] [JSN] |
| S3-260259 | Closing ENs for Solution #6 | pCR | InterDigital, Europe, Ltd. | 33.785 0.3.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-126 AI: 5.2.6 |
merged | [WTS] [JSN] |
| S3-260260 | SA#3 - KI#NEW - UE to CN Control Plane Security | pCR | InterDigital, Europe, Ltd. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260261 | SA#3 - KI#NEW - UE to CN User Plane Security | pCR | InterDigital, Europe, Ltd. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260262 | SA#3 - KI#NEW - UE to HPLMN Security | pCR | InterDigital, Europe, Ltd. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260263 | New SID on Mission Critical Next Generation Security |
SID new revised to S3-260860 |
Motorola Solutions UK Ltd. | Rel-20 |
S3-126 AI: 6.2 |
revised | [WTS] [JSN] | ||
| S3-260264 | New solution for SUCI calculation with symmetric key |
pCR revised to S3-260843 |
InterDigital, Inc. | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260265 | SA#5 - KI#NEW - Authentication and Authorization for 6G Access | pCR | InterDigital, Europe, Ltd. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260266 | Add algorithm type distinguisher to key derivation | CR | OPPO | 33.369 19.1.0 CR#79 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
merged | [WTS] [JSN] |
| S3-260267 | SA#5 - KI#NEW - Access-Agnostic Authentication for 6G | pCR | InterDigital, Europe, Ltd. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260268 | SA#5 - KI#NEW - Unified Framework for 6G Service-Level Authentication and Authorization | pCR | InterDigital, Europe, Ltd. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260269 | New solution on algorithm selection |
pCR revised to S3-260880 |
OPPO | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260270 | New solution on using NCAx as pure cipher algorithm |
pCR revised to S3-260882 |
OPPO | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260271 | SA#5 – KI#NEW - Subscriber Identifier Privacy in 6G | pCR | InterDigital, Inc. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260272 | New solution on using NCAx as pure integrity algorithm |
pCR revised to S3-260883 |
OPPO | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260273 | New solution on authentication |
pCR revised to S3-260816 |
OPPO | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260274 | Solution Update |
pCR revised to S3-260822 |
OPPO | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260275 | Annex B – Adding MAC CEs Risk Analysis | pCR | InterDigital, Inc. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260276 | MAC CEs Risk Analysis - a proposal for methodology and requirements | other | InterDigital, Inc. |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] | |||
| S3-260277 | SA#4 – KI#NEW - Security of Interworking Between 5GS and 6GS | pCR | InterDigital, Inc. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
withdrawn | [WTS] [JSN] |
| S3-260278 | Skeleton for TS 33.531(SCAS for CAPIF CF) |
draft TS revision of S3-260184 revised to S3-260970 |
Rakuten Mobile, Inc, BSI (DE) | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
revised | [WTS] [JSN] | |
| S3-260279 | [draft] Reply LS on Early Alignment on Access Stratum security aspects |
LS out LS is reply to LS S3-254013/R2-2507945 on Early Alignment on Access Stratum security aspects from RAN2 LS To: RAN2 |
Ericsson |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] | |||
| S3-260280 | Proportionality consideration for time and overhead critical MAC-CEs | discussion | Ericsson |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] | |||
| S3-260281 | MAC-CE questionnaire from SA3 to RAN2 | discussion | Ericsson |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] | |||
| S3-260282 | Pseudo-CR on MAC-CE risk analysis skeleton |
pCR revised to S3-260796 |
Ericsson | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260283 | Pseudo-CR on MAC-CE risk analysis skeleton description | pCR | Ericsson | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260284 | Pseudo-CR on Selective MAC-CE risk analysis in a table | pCR | Ericsson | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260285 | SA#5-KI#NEW-NSWO authentication in 6G |
pCR revised to S3-260751 |
CableLabs, Charter Communications, China Telecom, ZTE, Rogers, Comcast | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260286 | pCR CAPIF SCAS Section 4.2 | pCR | Rakuten Mobile, Inc, BSI (DE) | 33.531 0.1.1 | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] |
| S3-260287 | pCR CAPIF SCAS Section 4.3.1 | pCR | Rakuten Mobile, Inc, BSI (DE) | 33.531 0.1.1 | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] |
| S3-260288 | pCR CAPIF SCAS nested API | pCR | Rakuten Mobile, Inc, BSI (DE) | 33.531 0.1.1 | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] |
| S3-260289 | pCR to TS 33.502 - Security related Events for SBA parameters configuration | pCR | IIT Bombay | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
merged | [WTS] [JSN] |
| S3-260290 | LS reply to Out of sync t-ID handling for AIoT |
LS out LS is reply to S3-260108 LS To: CT4 |
Nokia | AmbientIoT-SEC | Rel-20 |
S3-126 AI: 3 |
merged | [WTS] [JSN] | |
| S3-260291 | Reply LS on Security parameter in A-IoT paging |
LS out LS is reply to S3-260110 LS To: RAN2 |
Nokia | AmbientIoT-SEC | Rel-20 |
S3-126 AI: 3 |
merged | [WTS] [JSN] | |
| S3-260292 | Resolution of EN on randomness of RAND_AIOT_d |
CR revised to S3-260756 |
Nokia | 33.369 19.1.0 CR#80 catD | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-260293 | Clarification of resynchronisation mechanism | CR | Nokia | 33.369 19.1.0 CR#81 catC | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 3 |
merged | [WTS] [JSN] |
| S3-260294 | Solution to KI#3 concerning privacy protection of DOA message |
pCR revised to S3-260825 |
Nokia | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260295 | Security aspects of localized service access | pCR | Nokia | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260296 | Discussion Paper on 6G Authentication Enhancements | discussion | Nokia | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] | |
| S3-260297 | New key issue on 6G authentication enhancements | pCR | Nokia | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260298 | New key issue on 6G re-authentication optimization | pCR | Nokia | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260299 | Annex B MAC-CE risk analysis |
pCR revised to S3-260799 |
Nokia, Samsung, ZTE, OPPO | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260300 | Reply LS on Out of sync T-ID handling for AIoT |
LS out LS is reply to S3-260108 LS To: CT4 |
ZTE Corporation | Rel-19 |
S3-126 AI: 3 |
merged | [WTS] [JSN] | ||
| S3-260301 | corrections for the re-synchronization of stored type T-ID | CR | ZTE Corporation | 33.369 19.1.0 CR#82 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 3 |
merged | [WTS] [JSN] |
| S3-260302 | Reply LS on user consent for data collection at the UE for NW-side model training |
LS out LS To: RAN2 |
ZTE Corporation | Rel-19 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-260303 | Corrections in TS 33.369 regarding AIoT Identification Information and Inventory Report message | CR | ZTE Corporation | 33.369 19.1.0 CR#83 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-260304 | Corrections of clause 5.3.4 in TS 33.369 regarding ciphered parameter | CR | ZTE Corporation | 33.369 19.1.0 CR#84 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
merged | [WTS] [JSN] |
| S3-260305 | Correction of clause Annex A.3 in TS 33.369 | CR | ZTE Corporation | 33.369 19.1.0 CR#85 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260306 | hybrid KEM based SUCI calculation |
pCR revised to S3-260899 |
ZTE Corporation | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260307 | Conclusion for KI#2 | pCR | ZTE Corporation | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260308 | Conclusion for KI#3 |
pCR revised to S3-260855 |
ZTE Corporation | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-260309 | Conclusion for KI#4 | pCR | ZTE Corporation | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260310 | Conclusion for KI#5 | pCR | ZTE Corporation | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260311 | Update conclusion for KI#1 | pCR | ZTE Corporation | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260312 | Update to KI#4 on active attacks in sensing | pCR | ZTE Corporation | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
merged | [WTS] [JSN] |
| S3-260313 | Update to KI#5 on unauthorized passive sensing | pCR | ZTE Corporation | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
merged | [WTS] [JSN] |
| S3-260314 | Conclusion for KI#1 | pCR | ZTE Corporation | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
noted | [WTS] [JSN] |
| S3-260315 | Resolve EN in solution #1 |
pCR revised to S3-260982 |
ZTE Corporation | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-260316 | Resolve EN in solution #2 |
pCR revised to S3-260983 |
ZTE Corporation | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-260317 | Resolve EN and add evaluation to solution #2 |
pCR revised to S3-260785 |
ZTE Corporation | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-260318 | Remove the EN in clause 4 to 6 |
pCR revised to S3-260948 |
ZTE Corporation | 33.758 0.1.0 | FS_PLMNNPN_Ph2 | Rel-20 |
S3-126 AI: 5.2.4 |
revised | [WTS] [JSN] |
| S3-260319 | Update the terms and abbreviations | pCR | ZTE Corporation | 33.758 0.1.0 | FS_PLMNNPN_Ph2 | Rel-20 |
S3-126 AI: 5.2.4 |
approved | [WTS] [JSN] |
| S3-260320 | Conclusion for key issue 1 | pCR | ZTE Corporation | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
noted | [WTS] [JSN] |
| S3-260321 | Solution on Authentication for AIoT devices | pCR | ZTE Corporation | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
merged | [WTS] [JSN] |
| S3-260322 | Evaluation for sol#6 | pCR | ZTE Corporation | 33.746 0.3.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
approved | [WTS] [JSN] |
| S3-260323 | Conclusions for KI#1 |
pCR revised to S3-260924 |
ZTE Corporation | 33.746 0.3.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
revised | [WTS] [JSN] |
| S3-260324 | Conclusions for KI#2 |
pCR revised to S3-260925 |
ZTE Corporation | 33.746 0.3.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
revised | [WTS] [JSN] |
| S3-260325 | Conclusions for KI#3 |
pCR revised to S3-260926 |
ZTE Corporation | 33.746 0.3.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
revised | [WTS] [JSN] |
| S3-260326 | Conclusions for KI#4 |
pCR revised to S3-260927 |
ZTE Corporation | 33.746 0.3.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
revised | [WTS] [JSN] |
| S3-260327 | Security threats analysis and security requirements for TR 33.704 | pCR | ZTE Corporation | 33.704 0.0.0 | FS_SCP | Rel-20 |
S3-126 AI: 5.2.15 |
noted | [WTS] [JSN] |
| S3-260328 | New key issue on MAC CE security | pCR | ZTE Corporation | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260329 | Updating introduction of security area#2 to include lower layer secuirty | pCR | ZTE Corporation | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260330 | New Security area for AI | pCR | ZTE Corporation | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260331 | Conclusion for KI#1 | pCR | ZTE Corporation | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260332 | Conclusion for KI#3 | pCR | ZTE Corporation | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260333 | resolve EN and add evaluation for solution #3 |
pCR revised to S3-260891 |
ZTE Corporation | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260334 | WID on Security Aspect for NR Femto Phase 2 |
WID new revised to S3-261008 |
ZTE Corporation | Rel-20 |
S3-126 AI: 6.1 |
revised | [WTS] [JSN] | ||
| S3-260335 | Security requirements for KI#1 |
pCR revised to S3-260949 |
China Telecommunications Corp.,, ZTE, Nokia | 33.758 0.1.0 | FS_PLMNNPN_Ph2 | Rel-20 |
S3-126 AI: 5.2.4 |
revised | [WTS] [JSN] |
| S3-260336 | Solution to TEID issue | pCR | China Telecommunications Corp., ZTE | 33.758 0.1.0 | FS_PLMNNPN_Ph2 | Rel-20 |
S3-126 AI: 5.2.4 |
noted | [WTS] [JSN] |
| S3-260337 | Solution to inter domain security on N9 interface |
pCR revised to S3-260950 |
China Telecommunications Corp., ZTE | 33.758 0.1.0 | FS_PLMNNPN_Ph2 | Rel-20 |
S3-126 AI: 5.2.4 |
revised | [WTS] [JSN] |
| S3-260338 | Conclusion to KI#1 | pCR | China Telecommunications Corp., ZTE, Nokia | 33.758 0.1.0 | FS_PLMNNPN_Ph2 | Rel-20 |
S3-126 AI: 5.2.4 |
noted | [WTS] [JSN] |
| S3-260339 | Conclusion to KI#2 | pCR | China Telecommunications Corp., ZTE | 33.758 0.1.0 | FS_PLMNNPN_Ph2 | Rel-20 |
S3-126 AI: 5.2.4 |
approved | [WTS] [JSN] |
| S3-260340 | SA#5 - update - update SA#5 introduction | pCR | China Telecommunications Corp. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260341 | SA#5 - KI#NEW - New Key Issue on authentication of UE for localized service access provided via PLMN | pCR | China Telecommunications Corp. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260342 | SA#4 - KI#NEW - New Key Issue on security between PLMN and localized network provided via PLMN | pCR | China Telecommunications Corp. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260343 | Reply LS on FS_APCOT study |
LS out LS is reply to S3-260126 source LS: S3-260126 LS To: SA6 |
Huawei, HiSilicon |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260344 | LS on KI for certificate unavailability |
LS out LS To: SA6 |
Huawei, HiSilicon | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
noted | [WTS] [JSN] | |
| S3-260345 | Updating KI #4 of TR 33.700-23 | pCR | Huawei, HiSilicon | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
merged | [WTS] [JSN] |
| S3-260346 | Updating clause 6 based on IETF progress | pCR | Huawei, HiSilicon | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260347 | Corrections for TR 33.703 |
pCR revised to S3-260811 |
Huawei, HiSilicon | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260348 | Overall evaluation for SUCI solutions |
pCR revised to S3-260918 |
Huawei, HiSilicon | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260349 | Updating Sol #1 for SUCI calculation | pCR | Huawei, HiSilicon, Apple | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260350 | Updating Sol #3 for SUCI calculation |
pCR revised to S3-260862 |
Huawei, HiSilicon | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260351 | Evaluation to solution #1 in TR 33.746 | draftCR | China Telecommunications Corp. | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
approved | [WTS] [JSN] | |
| S3-260352 | SA#3-KI#NEW-New KI on Security for 6G new NAS between UE and Core Network | pCR | China Telecommunications | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260353 | Conclusion to KI#1 in TR 33.746 | draftCR | China Telecommunications Corp. | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
merged | [WTS] [JSN] | |
| S3-260354 | Conclusion to KI#2 in TR 33.746 | draftCR | China Telecommunications Corp. | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
merged | [WTS] [JSN] | |
| S3-260355 | Conclusion to KI#3 in TR 33.746 | draftCR | China Telecommunications Corp. | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
merged | [WTS] [JSN] | |
| S3-260356 | New sol on security protection for N2 interface for NR Femto |
draftCR revised to S3-260921 |
China Telecommunications Corp. | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
revised | [WTS] [JSN] | |
| S3-260357 | New sol on security protection for N3 and N9 interface for NR Femto system |
draftCR revised to S3-260922 |
China Telecommunications Corp. | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
revised | [WTS] [JSN] | |
| S3-260358 | MAC CE questionare to R2 | discussion | Nokia |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] | |||
| S3-260359 | Description for core network security in clause 4.1 | pCR | Nokia | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260360 | Updates to Key Issue#1 |
pCR revised to S3-260920 |
Nokia, Samsung | 33.746 0.3.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
revised | [WTS] [JSN] |
| S3-260361 | SA#NEW Discussion paper on AI in 6G security and privacy | discussion | Nokia | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] | ||
| S3-260362 | Updates for Key Issue #2 | pCR | Nokia, Samsung | 33.724 0.2.0 | FS_NR_Femto_SEC_Ph2, FS_5G_WAB_SEC | Rel-20 |
S3-126 AI: 5.2.14 |
noted | [WTS] [JSN] |
| S3-260363 | SA#NEW Security area on AI-enabled 6G systems | pCR | IIT Bombay | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260364 | Updating solution#4 and add evaluation |
pCR revised to S3-260786 |
China Telecommunications | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-260365 | Annex-A Discussion Paper on attacker model handling | discussion | Nokia | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] | ||
| S3-260366 | Attacker Model update |
pCR revised to S3-261004 |
Nokia | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260367 | New WID on Security aspect of NSSAA in EPS | WID new | Nokia | Rel-20 |
S3-126 AI: 6.1 |
noted | [WTS] [JSN] | ||
| S3-260368 | Introducing security of NSSAA over EPC | CR | Nokia | 33.501 20.0.0 CR#2213 catB | DUMMY | Rel-20 |
S3-126 AI: 6.1 |
not pursued | [WTS] [JSN] |
| S3-260369 | New solution on T-ID based AIOT device privacy protection |
pCR revised to S3-260827 |
OPPO | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260370 | Sol7 update |
pCR revised to S3-260951 |
Ericsson | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-260371 | SA#NEW-New Security area on AI security for 6G | pCR | China Telecommunications | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260372 | Reply LS on Out of sync t-ID handling for AIoT |
LS out LS is reply to S3-260108 source LS: C4-255429 LS To: CT4 |
Huawei, HiSilicon | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 3 |
merged | [WTS] [JSN] | |
| S3-260373 | Update to Out of sync t-ID handling for AIoT | CR | Huawei, HiSilicon | 33.369 19.1.0 CR#86 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 3 |
merged | [WTS] [JSN] |
| S3-260374 | Update to the length of security parameters |
CR revised to S3-260977 |
Huawei, HiSilicon | 33.369 19.1.0 CR#87 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-260375 | update to solution#2 |
pCR revised to S3-260823 |
Huawei, HiSilicon | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260376 | new solution on ID privacy protection |
pCR revised to S3-260826 |
Huawei, HiSilicon | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260377 | conclusion on key issue #3 | pCR | Huawei, HiSilicon | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
noted | [WTS] [JSN] |
| S3-260378 | conclusion on key issue #4 | pCR | Huawei, HiSilicon | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
noted | [WTS] [JSN] |
| S3-260379 | update to solution#5 |
pCR revised to S3-260892 |
Huawei, HiSilicon | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260380 | update to solution#9 |
pCR revised to S3-260896 |
Huawei, HiSilicon | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260381 | general conclusion on the candidate 256bit algorithms | pCR | Huawei, HiSilicon | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260382 | Update the input parameter of enc and int keys |
CR revised to S3-260757 |
Huawei, HiSilicon | 33.369 19.1.0 CR#88 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-260383 | SA#3-update-update SA#3 description -update to the security area on UE to Core Network Security |
pCR revised to S3-260861 |
Huawei, HiSilicon | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260384 | SA#3-KI#new_new key issue on refreshing of temporary identifier | pCR | Huawei, HiSilicon | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260385 | AnnexB - Risk analysis for Activation/Deactivation of SCells | pCR | Huawei, HiSilicon | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260386 | AnnexB - Discussion paper on risk severity criteria of MAC CE | discussion | Huawei, HiSilicon | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] | |
| S3-260387 | SA#5-KI#new_new key issue on primary authentication optimization | pCR | Huawei, HiSilicon | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260388 | Conclusion on Key Issue#1 | pCR | Huawei, HiSilicon | 33.785 0.3.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-126 AI: 5.2.6 |
merged | [WTS] [JSN] |
| S3-260389 | Conclusion on Key Issue#2 | pCR | Huawei, HiSilicon | 33.785 0.3.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-126 AI: 5.2.6 |
merged | [WTS] [JSN] |
| S3-260390 | EN addressing and evaluation for solution#4 |
pCR revised to S3-260844 |
Huawei, HiSilicon | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260391 | Discussion about MIKEY SAKKE | discussion | Huawei, HiSilicon | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
noted | [WTS] [JSN] | |
| S3-260392 | Update to Current Work in IETF of IKEv2 | pCR | Huawei, HiSilicon | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260393 | EN addressing for solution #10 | pCR | Huawei, HiSilicon | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260394 | New solution about on-demand Extra-IV value derivation |
pCR revised to S3-260884 |
Huawei, HiSilicon | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260395 | Addressing key updating EN in sol#4 and updating evaluation |
pCR revised to S3-260942 |
Huawei, HiSilicon | 33.778 0.2.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-126 AI: 5.2.5 |
revised | [WTS] [JSN] |
| S3-260396 | Conclusion for MIKEY-SAKKE key exchange | pCR | Huawei, HiSilicon | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
merged | [WTS] [JSN] |
| S3-260397 | SA#3-KI#NEW-New key issue about concealing permanent or long-term subscription identifier | pCR | Huawei, HiSilicon, China Unicom | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260398 | New Solution for KI#1 Secure NAS messages via one pair of COUNTs |
pCR revised to S3-260832 |
Huawei, HiSilicon | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-260399 | Discussion Paper on security work for NAS message exchange with multiple satellites | discussion | Huawei, HiSilicon | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
noted | [WTS] [JSN] | |
| S3-260400 | Resolution of EN for sol.8 | pCR | Huawei, HiSilicon | 33.785 0.3.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-126 AI: 5.2.6 |
merged | [WTS] [JSN] |
| S3-260401 | Resolution for EN for RFC 9700 | pCR | Huawei, HiSilicon | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
merged | [WTS] [JSN] |
| S3-260402 | Resolution for EN for RFC 8725 |
pCR revised to S3-260842 |
Huawei, HiSilicon | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-260403 | Conclusion for BSP4SBA | pCR | Huawei, HiSilicon | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
noted | [WTS] [JSN] |
| S3-260404 | Offline CC Minutes of Meeting | discussion | Huawei, HiSilicon | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
noted | [WTS] [JSN] | |
| S3-260405 | SA#4 - Security Assumptions - add security assumption under SA#4 | pCR | Huawei, HiSilicon | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260406 | Solution to KI#3 of TR 33.777 | pCR | Huawei, HiSilicon | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260407 | Update to the Key Issue of sensing privacy | pCR | Huawei, HiSilicon | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260408 | Update to the Key Issues of signal attacks | pCR | Huawei, HiSilicon | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
merged | [WTS] [JSN] |
| S3-260409 | Reply LS on MANET multicast support |
LS out LS is reply to S3-260121 source LS: S2-2511306 LS To: SA2 revised to S3-260772 |
Huawei, HiSilicon | 5G_ProSe_Sec_Ph3 | Rel-20 |
S3-126 AI: 3 |
revised | [WTS] [JSN] | |
| S3-260410 | Update Solution#2.2 |
pCR revised to S3-260968 |
Huawei, HiSilicon | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-260411 | Update the conclusion of KI#1 |
pCR revised to S3-260853 |
Huawei, HiSilicon | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-260412 | Conclude the KI#2 | pCR | Huawei, HiSilicon | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260413 | Conclude to the privacy of sensing | pCR | Huawei, HiSilicon | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260414 | Conclude to the Key Issues of signal attacks |
pCR revised to S3-260857 |
Huawei, HiSilicon | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-260415 | SA#NEW - New security area on the security visibility | pCR | Huawei, HiSilicon, China Mobile, ZTE | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260416 | SA#1 - KI#NEW - New key issue on the security visibility | pCR | Huawei, HiSilicon | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260417 | Addressing roaming EN in sol#5 and updating evaluation |
pCR revised to S3-260944 |
Huawei, HiSilicon | 33.778 0.2.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-126 AI: 5.2.5 |
revised | [WTS] [JSN] |
| S3-260418 | Add conclusion to KI#1 | pCR | Huawei, HiSilicon | 33.724 0.2.0 | FS_5G_WAB_SEC | Rel-20 |
S3-126 AI: 5.2.14 |
noted | [WTS] [JSN] |
| S3-260419 | Living document to TS 33.511 |
draftCR revised to S3-260931 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-260420 | Living document to TS 33.512 |
draftCR revised to S3-260932 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-260421 | Living document to TS 33.513 | draftCR | Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260422 | Living document to TS 33.514 | draftCR | Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260423 | Living document to TS 33.517 | draftCR | Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260424 | Living document to TS 33.518 |
draftCR revised to S3-260937 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-260425 | Living document to TS 33.519 | draftCR | Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260426 | Living document to TS 33.521 |
draftCR revised to S3-260939 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-260427 | Living document to TR 33.926 |
draftCR revised to S3-260962 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-260428 | Living document to TS 33.116 | draftCR | Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260429 | Living document to TS 33.117 |
draftCR revised to S3-260956 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-260430 | AnnexB - proposal for a new annex content for B.2 on MAC CE methodology and risk analysis | pCR | Huawei, HiSilicon | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260431 | AnnexB - proposal for a new annex skeleton for Annex B on MAC CE | pCR | Huawei, HiSilicon | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260432 | AnnexB - proposal for content update for B.1 | pCR | Huawei, HiSilicon | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-260433 | SA#NEW - new security area proposal on AI | pCR | Huawei, HiSilicon, Lenovo, CATT, China Unicom | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260434 | SA#3 - KI#NEW- New key issue on security aspects for new NAS security under SA#3 | pCR | Huawei, HiSilicon | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260435 | SA#5 - Security Assumption - add security assumption under SA#5 | pCR | Huawei, HiSilicon | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260436 | withdrawn | pCR | Huawei, HiSilicon | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
withdrawn | [WTS] [JSN] |
| S3-260437 | withdrawn | pCR | Huawei, HiSilicon | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
withdrawn | [WTS] [JSN] |
| S3-260438 | Conclusion for KI#1 update | pCR | Ericsson | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260439 | pCR on evaluation of Sol#6 |
pCR revised to S3-260789 |
Nokia | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-260440 | Solution for KI#2 |
pCR revised to S3-260969 |
Ericsson | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-260441 | Conclusion on KI#4 AIOT ID protection | pCR | OPPO | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
noted | [WTS] [JSN] |
| S3-260442 | pCR on resolution of ENs and conclusion for Sol#11 |
pCR revised to S3-261001 |
Nokia | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-260443 | pCR on conclusion for KI#2 | pCR | Nokia | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
noted | [WTS] [JSN] |
| S3-260444 | Clause 4.1 - Add missing description of SA#4 |
pCR revised to S3-260812 |
Orange (Rapporteur) | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260445 | pCR on conclusion for KI#3 | pCR | Nokia | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
noted | [WTS] [JSN] |
| S3-260446 | pCR on KI#4 for CAPIF phase 4 | pCR | Nokia | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
merged | [WTS] [JSN] |
| S3-260447 | Conclusion for KI#2 | pCR | Ericsson | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260448 | LS on Security Requirements for 6G Roaming |
LS out LS To: GSMA NRG revised to S3-260795 |
Orange (Rapporteur) | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] | ||
| S3-260449 | New Solution for Key Issue #1 | pCR | Nokia | 33.746 0.3.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
approved | [WTS] [JSN] |
| S3-260450 | pCR on New KI on Location Security for CAPIF Ph4_SEC | pCR | Nokia | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
noted | [WTS] [JSN] |
| S3-260451 | New solution to detect compromised MWAB nodes using location tracking | pCR | Nokia | 33.724 0.2.0 | FS_5G_WAB_SEC | Rel-20 |
S3-126 AI: 5.2.14 |
noted | [WTS] [JSN] |
| S3-260452 | KI#2 update | pCR | Ericsson | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260453 | pCR on New solution for KI#2 | pCR | Nokia | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260454 | Conclusion for 33.730 |
pCR revised to S3-261000 |
Ericsson | 33.730 1.0.0 | FS_SCAS_CP | Rel-20 |
S3-126 AI: 5.2.8 |
revised | [WTS] [JSN] |
| S3-260455 | pCR on enhancing conclusions for KI#1 | pCR | Nokia | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260456 | Update R20 AIOT security scope |
pCR revised to S3-260814 |
OPPO | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260457 | pCR on EN resolution for Solution 1.5 |
pCR revised to S3-261007 |
Nokia | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-260458 | Revised SID for AIoT security ph2 | SID revised | OPPO | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 6.3 |
agreed | [WTS] [JSN] | |
| S3-260459 | Update to Overview of Security related Events Handling |
pCR revised to S3-260783 |
Huawei, HiSilicon | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-260460 | Clarification on key update of UE-Satellite-UE in IMS | CR | Huawei, HiSilicon | 33.328 19.2.0 CR#90 catF | 5GSAT_Ph3_SEC | Rel-19 |
S3-126 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-260461 | new SID on the security of IMS Architecture Enhancement | SID new | Huawei, HiSilicon, China Mobile, China Unicom | Rel-20 |
S3-126 AI: 6.2 |
noted | [WTS] [JSN] | ||
| S3-260462 | SA#5 - update - authorization and authentication of UE for localized service | pCR | Huawei, HiSilicon | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260463 | Clarification on the exact IE of producer PLMN ID verified by NF Producer | CR | Huawei, HiSilicon, BSI (DE) | 33.117 19.2.0 CR#229 catF | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
withdrawn | [WTS] [JSN] |
| S3-260464 | SA#5 - update - update SA#5 description on authentication and key agreement for applications | pCR | Huawei, HiSilicon, China Mobile, China Telecom, China Unicom | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260465 | pCR on adding different utilizations of containers for containerized network products |
pCR revised to S3-260996 |
Huawei, HiSilicon | 33.730 1.0.0 | FS_SCAS_CP | Rel-20 |
S3-126 AI: 5.2.8 |
revised | [WTS] [JSN] |
| S3-260466 | New key issue on NAS algorithm negotiation for 6G Network | pCR | Huawei, HiSilicon, China Telecom, China Unicom | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260467 | Resolving the ENs on Solution #2 |
pCR revised to S3-260767 |
Huawei, HiSilicon | 33.786 0.3.0 | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
revised | [WTS] [JSN] |
| S3-260468 | Conclusion for KI#1 | pCR | Huawei, HiSilicon | 33.786 0.3.0 | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
merged | [WTS] [JSN] |
| S3-260469 | Conclusion for KI#2 | pCR | Huawei, HiSilicon | 33.786 0.3.0 | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
merged | [WTS] [JSN] |
| S3-260470 | Address ENs in Sol#6 of TR 33.700-30 |
pCR revised to S3-260835 |
Huawei, HiSilicon | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-260471 | Conclusion for KI#1 | pCR | Huawei, HiSilicon | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
noted | [WTS] [JSN] |
| S3-260472 | Solution for KI #2 |
pCR revised to S3-260838 |
Huawei, HiSilicon | 33.724 0.2.0 | FS_5G_WAB_SEC | Rel-20 |
S3-126 AI: 5.2.14 |
revised | [WTS] [JSN] |
| S3-260473 | Clarification on the exact IE of producer PLMN ID verified by NF Producer | other | Huawei, HiSilicon, BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
noted | [WTS] [JSN] | |
| S3-260474 | Update Sol#3 of AIML | pCR | OPPO | 33.785 0.3.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-126 AI: 5.2.6 |
merged | [WTS] [JSN] |
| S3-260475 | SA#3 - KI#NEW - Security handling for new NAS protocol | pCR | LG Electronics | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260476 | EN Addition for solution #5 | pCR | LG Electronics | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260477 | EN Addition for solution #6 | pCR | LG Electronics | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260478 | Correct NRF test case for access token request verification |
other revised to S3-260935 |
Ericsson | SCAS_5GA |
S3-126 AI: 5.1.3 |
revised | [WTS] [JSN] | ||
| S3-260479 | Update Security area #3: UE to Core Network Security | pCR | OPPO | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260480 | Cleanup for solutions #5 of TR 33.785 | pCR | Xiaomi Communications | 33.785 0.3.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-126 AI: 5.2.6 |
merged | [WTS] [JSN] |
| S3-260481 | Cleanup for solutions #9 of TR 33.785 | pCR | Xiaomi Communications | 33.785 0.3.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-126 AI: 5.2.6 |
merged | [WTS] [JSN] |
| S3-260482 | Update solution #3 of TR 33.700-23 |
pCR revised to S3-260787 |
Xiaomi Communications | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-260483 | Update solution #8 of TR 33.700-23 |
pCR revised to S3-260790 |
Xiaomi Communications | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-260484 | Update solution #10 of TR 33.700-23 |
pCR revised to S3-260792 |
Xiaomi Communications | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-260485 | Update KI#1 conclusion of TR 33.777 | pCR | Xiaomi Communications | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260486 | Intermediate conclusion for KI#2 of TR 33.777 | pCR | Xiaomi Communications | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260487 | New solution for TR 33.777 KI#3 | pCR | Xiaomi Communications | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260488 | Intermediate conclusion for KI#3 of TR 33.777 | pCR | Xiaomi Communications | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260489 | Address the EN in solution #5 |
pCR revised to S3-260984 |
Beijing Xiaomi Mobile Software | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-260490 | Add the evaluation of solution #5 |
pCR revised to S3-260985 |
Beijing Xiaomi Mobile Software | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-260491 | Add the conclusion of KI#1 | pCR | Beijing Xiaomi Mobile Software | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
noted | [WTS] [JSN] |
| S3-260492 | New solution for UE Authorization during Intermediate UE selection |
pCR revised to S3-260829 |
Beijing Xiaomi Mobile Software | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260493 | New solution on authentication of DO-A capable device |
pCR revised to S3-260817 |
Beijing Xiaomi Mobile Software | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260494 | Address the ENs in solution #6 |
pCR revised to S3-260893 |
Beijing Xiaomi Mobile Software | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260495 | Add the evaluation of solution #6 |
pCR revised to S3-260894 |
Beijing Xiaomi Mobile Software | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260496 | SA#5 - KI#NEW - Re-authentication in roaming scenarios | pCR | Beijing Xiaomi Mobile Software | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260497 | SA#5 - KI#NEW - Subscriber identifier privacy | pCR | Beijing Xiaomi Mobile Software | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260498 | Evaluation for Solution #2 | pCR | Xiaomi EV Technology | 33.778 0.2.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-126 AI: 5.2.5 |
approved | [WTS] [JSN] |
| S3-260499 | Resolution of Editor’s Note in Solution #3 |
pCR revised to S3-260945 |
Xiaomi EV Technology | 33.778 0.2.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-126 AI: 5.2.5 |
revised | [WTS] [JSN] |
| S3-260500 | Update to Key Issue #4 |
pCR revised to S3-260856 |
Xiaomi EV Technology | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-260501 | Update to Key Issue #5 |
pCR revised to S3-260858 |
Xiaomi EV Technology | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-260502 | New Security Area on Sensing Security and Privacy | pCR | Xiaomi EV Technology | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260503 | Methodology to MAC CE Risk Analysis | pCR | Xiaomi EV Technology | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260504 | New Key Issue for SA#2 on Protection for Messages before AS Security | pCR | Xiaomi EV Technology | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260505 | New Key Issue for SA#2 on Security Enhancement for RAN Mobility |
pCR revised to S3-260810 |
Xiaomi EV Technology | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260506 | New Key Issue for SA#2 on Security Enhancement for RAN User Plane | pCR | Xiaomi EV Technology | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260507 | New Key Issue for SA#3 on Security for 6G NAS | pCR | Xiaomi EV Technology | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260508 | TR33703 - PQC - revision of Solution#1 | pCR | Apple | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260509 | TR33801-01- New KI on authentication request replay protection in Authentication Security areas | pCR | Apple | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260510 | TR33801-01- New KI on long term key leakage in Authentication Security areas | pCR | Apple | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260511 | TR33801-01- New KI on MAC layer security in RAN security | pCR | Apple | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260512 | TR33801-01 - draft_revised_annex B | pCR | Apple | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260513 | DP on MAC layer security methodology | discussion | Apple |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] | |||
| S3-260514 | AEAD - KI#1 revision |
pCR revised to S3-260878 |
Apple | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260515 | Reply LS to RAN2 on user consent for AI/ML network data collection(R2-2506541) |
LS out LS To: RAN2, RAN3, SA5 |
Apple | Rel-19 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-260516 | DP on user consent for AI/ML network data collection | discussion | Apple | Rel-19 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-260517 | SA#6 DP on security and privacy aspects of Network Exposure security Area | discussion | Nokia | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] | ||
| S3-260518 | pCR to merge all Hybrid solutions together | pCR | Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
noted | [WTS] [JSN] |
| S3-260519 | pCR to update solution #10 |
pCR revised to S3-260909 |
Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260520 | pCR to evaluation for solution #3 | pCR | Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
merged | [WTS] [JSN] |
| S3-260521 | pCR to evaluation for solution #4 | pCR | Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
merged | [WTS] [JSN] |
| S3-260522 | pCR to evaluation for solution #8 |
pCR revised to S3-260907 |
Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260523 | pCR to evaluation for solution #9 |
pCR revised to S3-260908 |
Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260524 | pCR to evaluation for solution #12 | pCR | Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
merged | [WTS] [JSN] |
| S3-260525 | pCR to evaluation for solution #13 |
pCR revised to S3-260914 |
Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260526 | pCR to evaluation for solution #14 |
pCR revised to S3-260999 |
Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260527 | pCR to evaluation for solution #11 |
pCR revised to S3-260910 |
Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260528 | pCR to evaluation for solution #15 | pCR | Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
noted | [WTS] [JSN] |
| S3-260529 | pCR for conclusion | pCR | Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
merged | [WTS] [JSN] |
| S3-260530 | pCR to unexpected messages in SBA | pCR | Samsung | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
merged | [WTS] [JSN] |
| S3-260531 | Conclusion on Key Issue #1 | pCR | Samsung | 33.778 0.2.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-126 AI: 5.2.5 |
noted | [WTS] [JSN] |
| S3-260532 | [TR 33.700-23] Resolving ENs in solution#5 |
pCR revised to S3-260788 |
Samsung | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-260533 | [TR 33.700-23] Conclusion for key issue#1 |
pCR revised to S3-260979 |
Samsung | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-260534 | Resolving ENs in solution#5 |
pCR revised to S3-260768 |
Samsung | 33.786 0.3.0 | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
revised | [WTS] [JSN] |
| S3-260535 | Conclusion for KI#1 and KI#2 |
pCR revised to S3-260770 |
Samsung | 33.786 0.3.0 | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
revised | [WTS] [JSN] |
| S3-260536 | SA#2 - Discussion paper on system information protection | discussion | Samsung | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] | |
| S3-260537 | SA#2 - KI#NEW - System Information protection/paging protection |
pCR revised to S3-260808 |
Samsung, SK Telecom | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260538 | SA#2 – KI#NEW – MAC CE protection | pCR | Samsung, SK Telecom | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260539 | SA#2 - KI#NEW - Initial RACH protection | pCR | Samsung, SK Telecom | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260540 | SA#2 - KI#NEW - Enhanced user plane security policy | pCR | Samsung | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260541 | SA#2 - KI#NEW - Decoupled user plane security in 6G RAN | pCR | Samsung | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260542 | SA#2 - KI#NEW - Key separation for RAN mobility | pCR | Samsung | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260543 | SA#3 - KI#NEW - Security for 6G control signalling | pCR | Samsung | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260544 | SA#3 - KI#NEW - Security for Interworking | pCR | Samsung | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260545 | SA#5 - KI#NEW - long-term credential update | pCR | Samsung, SK Telecom | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260546 | SA#5 - KI#NEW - Reducing dependency on long-term credential | pCR | Samsung, SK Telecom | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260547 | New sol on AIoT authentication |
pCR revised to S3-260819 |
Samsung | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260548 | New WID on Post-quantum Cryptography Migration |
WID new revised to S3-260761 |
Ericsson | Rel-20 |
S3-126 AI: 6.1 |
revised | [WTS] [JSN] | ||
| S3-260549 | Evaluation to Solution #11 |
pCR revised to S3-260911 |
Ericsson, Thales, Orange | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260550 | Addressing Editor’s Notes and adding Evaluation to Solution #7 |
pCR revised to S3-260906 |
Ericsson | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260551 | Analyzing solutions for quantum resistant SUCIs | pCR | Ericsson | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
merged | [WTS] [JSN] |
| S3-260552 | SA#NEW - New Security Area on Security and privacy of cellular IoT enablers in 6G | pCR | Ericsson | 33.801-01 5.3.1 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260553 | Update SA#1 Add new security aspects | pCR | CATT | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260554 | new solution on Security protection for MWAB nodes | pCR | China Telecom Corporation Ltd. | 33.724 0.2.0 | FS_5G_WAB_SEC | Rel-20 |
S3-126 AI: 5.2.14 |
noted | [WTS] [JSN] |
| S3-260555 | Update SA#2 Add new security aspects | pCR | CATT | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260556 | SA#6 - Update - addition of SA6 reference |
pCR revised to S3-260863 |
Nokia | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260557 | new solution on Detection of compromised WAB node | pCR | China Telecom Corporation Ltd. | 33.724 0.2.0 | FS_5G_WAB_SEC | Rel-20 |
S3-126 AI: 5.2.14 |
noted | [WTS] [JSN] |
| S3-260558 | Update SA#5 Add new security aspects |
pCR revised to S3-260929 |
CATT | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260559 | Evaluation of solution #1 | pCR | Thales, ORANGE, Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260560 | Evaluation of solution #5 |
pCR revised to S3-260904 |
Thales, ORANGE, Samsung, NCSC | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260561 | Evaluation of solution #6 |
pCR revised to S3-260905 |
Thales, ORANGE, Samsung, NCSC | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260562 | New Solution for Key Issue #4 |
pCR revised to S3-260923 |
Nokia | 33.746 0.3.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
revised | [WTS] [JSN] |
| S3-260563 | Evaluation of solution #8 | pCR | Thales, ORANGE | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-260564 | CR to TS33.369 define the length of (X)RES | CR | CATT | 33.369 19.1.0 CR#89 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
merged | [WTS] [JSN] |
| S3-260565 | Evaluation of solution #12 | pCR | Thales, ORANGE | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-260566 | Evaluation of solution #15 | pCR | Thales, ORANGE | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-260567 | CR to TS33.369 define the length of T-ID | CR | CATT | 33.369 19.1.0 CR#90 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
merged | [WTS] [JSN] |
| S3-260568 | KI#2: solution for DO-A capable AIoT devices |
pCR revised to S3-260815 |
Thales, ZTE | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260569 | New solution on DO-A capable AIoT Device communication protection |
pCR revised to S3-260824 |
CATT | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260570 | New solution on DO-A capable AIoT Device registration procedure |
pCR revised to S3-260820 |
CATT | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260571 | SA#NEW - New Security Area on AI Security | pCR | Ericsson | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260572 | SA#NEW - New Security Area on Data Framework Security | pCR | Ericsson | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260573 | Pseudo-CR on Resolving ENs in Solution #11 | pCR | Ericsson | 33.785 0.3.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-126 AI: 5.2.6 |
merged | [WTS] [JSN] |
| S3-260574 | Conclusion for MPQUIC study | pCR | Ericsson, Qualcomm Incorporated | 33.778 0.2.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-126 AI: 5.2.5 |
noted | [WTS] [JSN] |
| S3-260575 | Pseudo-CR on Key Issue 4 Update | pCR | Ericsson | 33.724 0.2.0 | FS_5G_WAB_SEC | Rel-20 |
S3-126 AI: 5.2.14 |
approved | [WTS] [JSN] |
| S3-260576 | Psuedo-CR on New Solution for KI#4 | pCR | Ericsson | 33.724 0.2.0 | FS_5G_WAB_SEC | Rel-20 |
S3-126 AI: 5.2.14 |
approved | [WTS] [JSN] |
| S3-260577 | Pesudo-CR on New Solution for KI#1 |
pCR revised to S3-260837 |
Ericsson | 33.724 0.2.0 | FS_5G_WAB_SEC | Rel-20 |
S3-126 AI: 5.2.14 |
revised | [WTS] [JSN] |
| S3-260578 | Pseudo-CR on New Solution for Key Issue #3 | pCR | Ericsson | 33.724 0.2.0 | FS_5G_WAB_SEC | Rel-20 |
S3-126 AI: 5.2.14 |
approved | [WTS] [JSN] |
| S3-260579 | New solution on DO-A capable AIoT Device security handling in mobility | pCR | CATT | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
noted | [WTS] [JSN] |
| S3-260580 | New solution on download task management for S&F operations | pCR | CATT | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
noted | [WTS] [JSN] |
| S3-260581 | New solution on NAS keys isolation in S&F operations |
pCR revised to S3-260928 |
CATT | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-260582 | skeleton of security configuration provisioning |
draft TR revised to S3-260851 |
China Mobile | FS_SCP | Rel-20 |
S3-126 AI: 5.2.15 |
revised | [WTS] [JSN] | |
| S3-260583 | pcr on scope for security configuration provisioning |
pCR revised to S3-260852 |
China Mobile | 33.704 0.0.0 | FS_SCP | Rel-20 |
S3-126 AI: 5.2.15 |
revised | [WTS] [JSN] |
| S3-260584 | SA5-KI new-legacy USIM authentication | pCR | China Mobile | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260585 | Protection of information transferring between private and public network to support type 1 AIoT Devices in topology 2 | pCR | China Mobile | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
noted | [WTS] [JSN] |
| S3-260586 | Update Solution#3 for removing ENs and adding evaluation | pCR | CATT | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-260587 | Discussion Paper on MAC CE Privacy Leakage Combined with C-RNTI | discussion | Xidian University, OPPO | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] | ||
| S3-260588 | Draft reply LS- Early Alignment on Access Stratum security aspects |
LS out LS is reply to S3-254013 LS To: RAN2 |
OPPO, Samsung | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] | ||
| S3-260589 | DP on PHY Layer Sensing Signals in 6G | discussion | OPPO, BUPT, ST Engineering iDirect | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] | ||
| S3-260590 | New sol on using NCAx as cipher and integrity algorithm |
pCR revised to S3-260885 |
OPPO | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260591 | 6G Sensing Security Area Update | pCR | OPPO, CMCC | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260592 | Update Sol#7 DO-A Capable AIoT Device Identifier Protection with Bloom Filter | pCR | Xidian, OPPO | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260593 | Update KI#5 of AIOT | pCR | OPPO | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
noted | [WTS] [JSN] |
| S3-260594 | Pseudo-CR on defining terms for TR 33.771 |
pCR revised to S3-260872 |
Qualcomm Incorporated | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260595 | Pseudo-CR on solution for supporting AEAD mode |
pCR revised to S3-260879 |
Qualcomm Incorporated | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260596 | Adding a note to solution #3 | pCR | Qualcomm Incorporated | 33.746 0.3.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
approved | [WTS] [JSN] |
| S3-260597 | Updates on T-ID terminology of TS 33.369 | CR | Qualcomm Incorporated | 33.369 19.1.0 CR#91 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
merged | [WTS] [JSN] |
| S3-260598 | Authentication procedure for DO-A capable AIoT devices |
pCR revised to S3-260821 |
Qualcomm Incorporated | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260599 | Protection of information for DO-A capable AIoT devices |
pCR revised to S3-260980 |
Qualcomm Incorporated | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260600 | Adding scope |
pCR revised to S3-260981 |
Qualcomm Incorporated | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-260601 | New solution to the NAS key stream re-use issue during S&F operations |
pCR revised to S3-260834 |
Qualcomm Incorporated | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-260602 | Pseudo-CR on ECIES-MLKEM Hybrid SUCI Calculation |
pCR revised to S3-260900 |
Qualcomm Incorporated | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260603 | Pseudo-CR on ECKEM-MLKEM Hybrid SUCI Calculation |
pCR revised to S3-260901 |
Qualcomm Incorporated | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260604 | Pseudo-CR on Backward Compatible Hybrid SUCI Calculation |
pCR revised to S3-260902 |
Qualcomm Incorporated | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260605 | SA#2 – KI#NEW - Security for RAN mobility | pCR | Qualcomm Incorporated | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260606 | SA#2 – KI#NEW - User-plane security in 6G RAN | pCR | Qualcomm Incorporated | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260607 | SA#2 – KI#NEW - Robust AS security setup | pCR | Qualcomm Incorporated | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260608 | SA#1 – KI#NEW - KDF agility | pCR | Qualcomm Incorporated | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260609 | SA#2 – Discussion - Way forward for MAC CE security | discussion | Qualcomm Incorporated |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] | |||
| S3-260610 | SA#2 – KI#NEW - MAC CE security |
pCR revised to S3-260802 |
Qualcomm Incorporated | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260611 | Reply LS on IMS Data Channel LI requirements |
LS out LS is reply to S3-260122 LS To: SA3-LI, SA2 |
Ericsson | NG_RTC_SEC_Ph2 | Rel-19 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |
| S3-260612 | Way forward for the IMS Data Channel and LI cases | discussion | Ericsson | NG_RTC_SEC_Ph2 | Rel-19 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |
| S3-260613 | Corrections for IMS Data Channels and LI | CR | Ericsson | 33.328 19.2.0 CR#91 catC | NG_RTC_SEC_Ph2 | Rel-19 |
S3-126 AI: 3 |
not pursued | [WTS] [JSN] |
| S3-260614 | Removing Editor's Note on determining NF Consumer for Authentication Failure | pCR | Ericsson | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
merged | [WTS] [JSN] |
| S3-260615 | Message type of malformed messages and massive number of messages | pCR | Ericsson | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-260616 | Alignment and clarification of the message IE | pCR | Ericsson, Vodafone | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-260617 | Event instance identifier and clarification of event number/event code |
pCR revised to S3-260781 |
Ericsson, Vodafone | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-260618 | Clarification of the security event related to massive number of incoming messages |
pCR revised to S3-260782 |
Ericsson | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-260619 | Align terminology to "trust domain" | pCR | Ericsson | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-260620 | Configuration related information | pCR | Ericsson | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
merged | [WTS] [JSN] |
| S3-260621 | Annex#A - Proposal for an Attacker model methodology for the 6G study | pCR | Ericsson | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260622 | Annex#A - Pseudo-CR providing an Attacker model definition |
pCR revised to S3-261005 |
Ericsson | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260623 | Annex#A - Pseudo-CR providing an example of an Attacker model | pCR | Ericsson | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260624 | New Security Area on Data collection for security monitoring |
pCR revised to S3-260864 |
Ericsson, AT&T, Lenovo, Motorola Mobility, NSA, T-Mobile US, Nokia, SK Telecom, Deutsche Telekom | 33.801-01 5.3.1 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260625 | SA#1 - Security Assumptions - Add security assumptions for a serving network security anchor |
pCR revised to S3-260867 |
Ericsson | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260626 | New SID on the security support for the Next Generation Real Time Communication services Phase 3 | SID new | Ericsson | Rel-20 |
S3-126 AI: 6.1 |
noted | [WTS] [JSN] | ||
| S3-260627 | New WID on the security support for the Next Generation Real Time Communication services Phase 3 | WID new | Ericsson | Rel-20 |
S3-126 AI: 6.1 |
noted | [WTS] [JSN] | ||
| S3-260628 | Length of RESAIOT in AIOT | CR | Ericsson | 33.369 19.1.0 CR#92 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
merged | [WTS] [JSN] |
| S3-260629 | Length of T-ID in AIoT | CR | Ericsson | 33.369 19.1.0 CR#93 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
merged | [WTS] [JSN] |
| S3-260630 | Reply LS on Security parameter in A-IoT paging |
LS out LS is reply to S3-260110 LS To: RAN2 revised to S3-260755 |
Ericsson, Orange | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 3 |
revised | [WTS] [JSN] | |
| S3-260631 | New solution to KI#2: AKA-based authentication for inventory, command and registration |
pCR revised to S3-260818 |
Ericsson | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260632 | Updating potential security requirements in key issue on resource exhaustion | pCR | Ericsson | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
noted | [WTS] [JSN] |
| S3-260633 | Solution to Amplification of resource exhaustion | pCR | Ericsson | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
noted | [WTS] [JSN] |
| S3-260634 | DP on Configuration of AIOT devices for privacy protection | discussion | Ericsson | Rel-19 |
S3-126 AI: 4.1.1 |
noted | [WTS] [JSN] | ||
| S3-260635 | CR on Configuration of AIOT devices for privacy protection | CR | Ericsson | 33.369 19.1.0 CR#94 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-260636 | Resolving Editor’s Note in Solution-1 Accessing Group Resources | pCR | Ericsson | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-260637 | Resolving Editors’ Note in Solution-7 Open Discover Service APIs |
pCR revised to S3-260791 |
Ericsson | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-260638 | Resolving Editors’ Note in Solution-9 Scope Parameter with Purpose Information |
pCR revised to S3-260793 |
Ericsson | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-260639 | Update to KI#4 Credentials Unavailability |
pCR revised to S3-260794 |
Ericsson | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-260640 | New Solution for KI#4 “Fixing Certificate Related Problems” | pCR | Ericsson | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
noted | [WTS] [JSN] |
| S3-260641 | New Key Issue on secure AIoT device context expiry | pCR | Ericsson | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
noted | [WTS] [JSN] |
| S3-260642 | Addressing EN in Solution #6 for group paging using Bloom filter |
pCR revised to S3-260828 |
Ericsson | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260643 | pCR SCAS CAPIF Scope and Clause 4.1 | pCR | Rakuten Mobile, Inc, BSI(DE) | 33.531 0.1.1 | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] |
| S3-260644 | SA#NEW - DP on Subscriber Permission study requirements | discussion | Nokia |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] | |||
| S3-260645 | Add the missing Core Network security area description | pCR | China Mobile Com. Corporation | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260646 | SA#4 - KI#NEW - New KI under SA#4 | pCR | China Mobile Com. Corporation | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
withdrawn | [WTS] [JSN] |
| S3-260647 | SA#NEW - security area on Subscriber Permission and Application User Consent | pCR | Nokia | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260648 | SA#4 - KI#NEW - New KI under SA#4 | pCR | China Mobile, Deutsche Telekom | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260649 | SA#5 - KI#NEW - New KI under SA#5 | pCR | China Mobile, vivo | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260650 | pCR on TS 33.117 protection against brute force and dict. attacks |
other revised to S3-260954 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-260651 | pCR on TS 33.117 client credential assertion validation | other | BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260652 | pCR on TS 33.117 protection of transport layer |
other revised to S3-260955 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-260653 | pCR on TS 33.117 security event logging |
other revised to S3-260997 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-260654 | pCR on TS 33.117 for TC_NO_UNUSED_HTTP_METHODS |
other revised to S3-260998 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-260655 | Correction of 33.515 TC_CHARGING_ID_UNIQUENESS_SMF pre-conditions |
draftCR revised to S3-260958 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-260656 | Correction of 33.515 TC_UP_SECURITY_POLICY_SMF expected results | draftCR | BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260657 | Living document for TS 33.523 | draftCR | BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260658 | Living document for TS 33.226 | draftCR | BSI (DE), Montsecure, Deutsche Telekom | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260659 | pCR on TR 33.730 completion of Security requirements related to logging | other | BSI (DE) | FS_SCAS_CP | Rel-20 |
S3-126 AI: 5.2.8 |
approved | [WTS] [JSN] | |
| S3-260660 | pCR on TR 33.730 completion of trusted image repo test case |
other revised to S3-260987 |
BSI (DE) | FS_SCAS_CP | Rel-20 |
S3-126 AI: 5.2.8 |
revised | [WTS] [JSN] | |
| S3-260661 | pCR on TR 33.730 completion of vulnerability scanning or containerized NF |
other revised to S3-260988 |
BSI (DE) | FS_SCAS_CP | Rel-20 |
S3-126 AI: 5.2.8 |
revised | [WTS] [JSN] | |
| S3-260662 | pCR on TR 33.730 completion of Containerized NF run-time security |
other revised to S3-260989 |
BSI (DE) | FS_SCAS_CP | Rel-20 |
S3-126 AI: 5.2.8 |
revised | [WTS] [JSN] | |
| S3-260663 | pCR on TR 33.730 completion of Data protection in containerized NF | other | BSI (DE) | FS_SCAS_CP | Rel-20 |
S3-126 AI: 5.2.8 |
approved | [WTS] [JSN] | |
| S3-260664 | pCR on TR 33.730 new test on Resource quotas and limits enforcement |
other revised to S3-260990 |
BSI (DE) | FS_SCAS_CP | Rel-20 |
S3-126 AI: 5.2.8 |
revised | [WTS] [JSN] | |
| S3-260665 | pCR on TR 33.730 new test on Pod security policy enforcement | other | BSI (DE) | FS_SCAS_CP | Rel-20 |
S3-126 AI: 5.2.8 |
noted | [WTS] [JSN] | |
| S3-260666 | pCR on TR 33.730 container SCAS conclusion | other | BSI (DE) | FS_SCAS_CP | Rel-20 |
S3-126 AI: 5.2.8 |
merged | [WTS] [JSN] | |
| S3-260667 | New threat for CAPIF nested API | other | Rakuten Mobile, Inc, BSI(DE) | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] | |
| S3-260668 | Correction of misalignment with TS 29.510: Replace appended PLMN ID access token claims with PLMN ID specific claims in roaming |
CR revised to S3-260760 |
Ericsson, Nokia | 33.501 20.0.0 CR#2214 catF | TEI20 | Rel-20 |
S3-126 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-260669 | Pseudo-CR on Resolving editor's notes for RFC 8725 best practices | pCR | Ericsson | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
merged | [WTS] [JSN] |
| S3-260670 | Pseudo-CR on Resolving editor's notes for RFC 9700 best practices |
pCR revised to S3-260839 |
Ericsson | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-260671 | Pseudo-CR on Best security practice on using UTF-8 | pCR | Ericsson | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-260672 | Pseudo-CR on Best security practice on using end-to-end TLS between the client and the resource server |
pCR revised to S3-260845 |
Ericsson | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-260673 | Pseudo-CR on Best security practice on transmission of authorization responses | pCR | Ericsson | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
noted | [WTS] [JSN] |
| S3-260674 | Pseudo-CR on Best security practice on configuration of client_id | pCR | Ericsson,Nokia | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-260675 | Pseudo-CR on Best security practice on sender-constrained access tokens |
pCR revised to S3-260847 |
Ericsson | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-260676 | Pseudo-CR on Best security practice on performing algorithm verification | pCR | Ericsson | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-260677 | Pseudo-CR on Best security practice on validating all cryptographic operations |
pCR revised to S3-261002 |
Ericsson | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-260678 | SA#5-KI#NEW-New KI under SA#5-Key issue on subscriber identity privacy | pCR | China Mobile Com. Corporation | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260679 | Correction of reference numbering | CR | Nokia | 33.501 15.18.0 CR#2215 catF | 5GS_Ph1-SEC | Rel-15 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260680 | Way forward for the application of AEAD | discussion | China Mobile Com. Corporation | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] | |
| S3-260681 | Correction of reference numbering | CR | Nokia | 33.501 16.18.0 CR#2216 catA | 5GS_Ph1-SEC | Rel-16 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260682 | Correction of reference numbering | CR | Nokia | 33.501 17.14.0 CR#2217 catA | 5GS_Ph1-SEC | Rel-17 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260683 | Conclusions for IKEv2 |
pCR revised to S3-260917 |
China Mobile Com. Corporation | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260684 | Correction of reference numbering | CR | Nokia | 33.501 18.10.0 CR#2218 catA | 5GS_Ph1-SEC | Rel-18 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260685 | Adding definitions | pCR | Ericsson | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
merged | [WTS] [JSN] |
| S3-260686 | New KI on authenticated encryption |
pCR revised to S3-260877 |
Ericsson | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260687 | New Solution for KI#1 | pCR | Ericsson | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260688 | Update of Annex A | pCR | Ericsson | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260689 | New Solution for KI on authenticated encryption | pCR | Ericsson | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260690 | New Solution for KI#2 |
pCR revised to S3-260886 |
Ericsson | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260691 | New SID on Security of application user consent architecture |
SID new revised to S3-260762 |
Ericsson, Interdigital | Rel-20 |
S3-126 AI: 6.1 |
revised | [WTS] [JSN] | ||
| S3-260692 | Reply LS on FS_APCOT study |
LS out LS is reply to S3-260126 LS To: SA6 |
Ericsson | Rel-20 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-260693 | Resolving ENs and evaluation of solution#3 |
pCR revised to S3-260769 |
Ericsson | 33.786 0.3.0 | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
revised | [WTS] [JSN] |
| S3-260694 | Revisiting the structure of 256-bit algorithms specifications | discussion | Ericsson | 256_Algo |
S3-126 AI: 4.1.1 |
noted | [WTS] [JSN] | ||
| S3-260695 | Correction of reference numbering in TS 33.501 | CR | Nokia | 33.501 19.5.0 CR#2219 catA | 5GS_Ph1-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260696 | A hybrid scheme for SUPI protection |
pCR revised to S3-260859 |
China Mobile Com. Corporation | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260697 | Correction of reference numbering | CR | Nokia | 33.501 20.0.0 CR#2220 catA | 5GS_Ph1-SEC | Rel-20 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260698 | New WID on 5G Security Assurance Specification (SCAS) for the Container-based Products | WID new | Ericsson, BSI (DE) | Rel-20 |
S3-126 AI: 6.1 |
noted | [WTS] [JSN] | ||
| S3-260699 | Solution to KI#3 |
pCR revised to S3-260887 |
Lenovo, Motorola Mobility | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-260700 | EN removal and evaluation for solution #7 |
pCR revised to S3-260986 |
Nokia | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-260701 | pCR for 33.117 Clean-up | other | BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260702 | pCR for 33.117 overload situations | other | BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260703 | pCR for 33.512 Cleanup of TC NAS NULL integrity protection | other | BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260704 | pCR for 33.512 Specify NIA selection and use | other | BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260705 | Pseudo-CR on Security Assurance Specification (SCAS) for CAPIF Core Function section 4.2 and 4.3 | other | BSI (DE), Rakuten Mobile Inc. | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] | |
| S3-260706 | Add new CAPIF CF test case that verifies whether AEF_PSK is computed correctly by the CAPIF CF |
other revised to S3-260972 |
BSI (DE), Montsecure, Rakuten Mobile Inc. | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
revised | [WTS] [JSN] | |
| S3-260707 | Add new CAPIF CF test case that verifies whether the onboard credential is correctly validated |
other revised to S3-260941 |
BSI (DE), Montsecure, Rakuten Mobile Inc. | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
revised | [WTS] [JSN] | |
| S3-260708 | Add new AEF test case that verifies whether revocation of an access token in an RNAA enabled CAPIF deployment is correctly implemented |
other revised to S3-260936 |
BSI (DE), Montsecure, Rakuten Mobile Inc. | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
revised | [WTS] [JSN] | |
| S3-260709 | Add new API Exposing Function test case that verifies whether the API Exposing Function correctly validates the resOwnerId claim when Resource owner-aware Northbound API Access is used |
other revised to S3-260973 |
BSI (DE), Montsecure, Rakuten Mobile Inc. | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
revised | [WTS] [JSN] | |
| S3-260710 | pCR on TS 33.926 adding threat for AEF_PSK TC for CCF | other | BSI (DE), Montsecure, Rakuten Mobile Inc. | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] | |
| S3-260711 | pCR for 33.926 Add threat framework for CCF | other | BSI (DE), Montsecure | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] | |
| S3-260712 | pCR on TS 33.926 adding threat for OAuth TC for CCF | other | BSI (DE), Montsecure, Rakuten Mobile Inc. | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] | |
| S3-260713 | pCR on TS 33.926 adding threat for validation resOwnerId TC for CCF | other | BSI (DE), Montsecure, Rakuten Mobile Inc. | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] | |
| S3-260714 | pCR on TS 33.926 adding threat for rnaa revocation TC for CCF | other | BSI (DE), Montsecure, Rakuten Mobile Inc. | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] | |
| S3-260715 | Way forward for MAC CE security including pCR |
pCR revised to S3-260797 |
NTT DOCOMO INC.. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260716 | Update to SA3 ToR |
ToR revised to S3-260754 |
SA3 Chair |
S3-126 AI: 3 |
revised | [WTS] [JSN] | |||
| S3-260717 | Further details and EN removal for Solution #4 | pCR | Sateliot, Novamint | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-260718 | Further details and EN removal for Solution #8 | pCR | Sateliot, Novamint | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-260719 | Update to 6G exposure security area | pCR | Ericsson | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-260720 | Pseudo-CR on MIKEY-SAKKE PQC evaluation |
pCR revision of S3-260235 revised to S3-260916 |
Motorola Solutions UK Ltd. | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-260721 | New solution on authorization of intermediate UE for 5G Ambient IoT |
pCR revised to S3-260830 |
OPPO | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-260722 | Discussion on passive attacker on 5GA sensing signals | discussion | OPPO | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] | |
| S3-260723 | Considerations on MAC CEs in 6G | discussion | VODAFONE | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] | |
| S3-260724 | Discussion on active attacker on 5GA sensing signals | discussion | OPPO | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] | |
| S3-260725 | EN removal for solution #4 | pCR | Nokia | 33.746 0.3.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
approved | [WTS] [JSN] |
| S3-260726 | Remove ENs in KI #4 and KI #5 | pCR | OPPO | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
merged | [WTS] [JSN] |
| S3-260727 | Update conclusion for KI#1 in TR 33.777 | pCR | OPPO | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260728 | Conclusion for KI #2 in TR 33.777 |
pCR revised to S3-260854 |
OPPO | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-260729 | [draft] Reply LS on User consent for Data collection at the UE for NW-side model training |
LS out LS is reply to S3-260109 source LS: R2-2506541 LS To: RAN2 |
Ericsson | Rel-19 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-260730 | LS on security of FS_APCOT study |
LS out LS is reply to S3-260126 source LS: S6-255645 LS To: SA6 |
Nokia |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-260731 | Evaluation of solution #16 | pCR | Thales, ORANGE | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-260732 | New SID on security aspects of APCOT | SID new | Nokia |
S3-126 AI: 6.1 |
merged | [WTS] [JSN] | |||
| S3-260733 | Draft TS 33.547 | pCR | CATT | 33.547 0.2.0 | SCAS_Femto_SeGW | Rel-20 |
S3-126 AI: 5.1.6 |
endorsed | [WTS] [JSN] |
| S3-260734 | Living document to TR 33.926 | pCR | CATT | 33.547 0.2.0 | SCAS_Femto_SeGW | Rel-20 |
S3-126 AI: 5.1.6 |
approved | [WTS] [JSN] |
| S3-260735 | SA#NEW- Security Area on Subscriber Permission | pCR | CATT | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260736 | SA#5 - KI# NEW - New KI on security and privacy of identification for entities beyond subscription | pCR | CATT | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260737 | SA#3-KI#NEW- New KI on 6G New NAS security | pCR | CATT | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260738 | Update_soultion4 | pCR | CATT | 33.785 0.1.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-126 AI: 5.2.6 |
merged | [WTS] [JSN] |
| S3-260739 | Replay prevention |
pCR revised to S3-260841 |
Nokia | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-260740 | Conclusion for KI #1 in TR 33.700-30 | pCR | OPPO | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
noted | [WTS] [JSN] |
| S3-260741 | Additional suggestion to the resolution for EN for RFC 8725 | pCR | Nokia | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
merged | [WTS] [JSN] |
| S3-260742 | Editorial updates | pCR | Nokia | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-260743 | References | pCR | Nokia | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-260744 | Scope |
pCR revised to S3-260848 |
Nokia | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-260745 | SA#NEW- AI Security |
pCR revised to S3-260865 |
Nokia | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-260746 | Overview |
pCR revised to S3-260849 |
Nokia | 33.755 0.2.0 | GROUPE, FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-260747 | DP on SBA core network, interconnect and roaming | discussion | Nokia |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] | |||
| S3-260748 | KI for SBA, Interconnect and Roaming | pCR | Nokia | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260749 | Solution to KI#2 | pCR | Lenovo, Motorola Mobility | 33.724 0.2.0 | FS_5G_WAB_SEC | Rel-20 |
S3-126 AI: 5.2.14 |
noted | [WTS] [JSN] |
| S3-260750 | pCR to TS 33.801 - Security of Computing Support | pCR | IIT Bombay | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260751 | SA#5-KI#NEW-NSWO authentication in 6G |
pCR revision of S3-260285 |
CableLabs, Charter Communications, China Telecom, ZTE, Rogers, Comcast, Nokia | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260752 | SA#3 – KI#NEW - Security of Interworking Between 5GS and 6GS | pCR | InterDigital, Inc. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-260753 | LS on LI requirements |
LS in source LS: s3i260049 |
SA3-LI |
S3-126 AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-260754 | Update to SA3 ToR |
ToR revision of S3-260716 |
SA3 Chair |
S3-126 AI: 3 |
agreed | [WTS] [JSN] | |||
| S3-260755 | Reply LS on Security parameter in A-IoT paging |
LS out LS is reply to S3-260110 LS To: RAN2 revision of S3-260630 |
Ericsson, Orange | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 3 |
noted | [WTS] [JSN] | |
| S3-260756 | Resolution of EN on randomness of RAND_AIOT_d |
CR revision of S3-260292 |
Nokia | 33.369 19.1.0 CR#801 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260757 | Update the input parameter of enc and int keys |
CR revision of S3-260382 |
Huawei, HiSilicon | 33.369 19.1.0 CR#881 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260758 | Correction on clause 6.4.6-R19 | CR | vivo | 33.501 20.0.0 CR#2221 catA | 5GS_Ph1-SEC | Rel-20 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260759 | MCX ETSI Plugtest Observations | other | SA3 | MCXSec3 | Rel-18 |
S3-126 AI: 4.1.1 |
endorsed | [WTS] [JSN] | |
| S3-260760 | Correction of misalignment with TS 29.510: Replace appended PLMN ID access token claims with PLMN ID specific claims in roaming |
CR revision of S3-260668 |
Ericsson, Nokia | 33.501 20.0.0 CR#22141 catA | TEI19 | Rel-20 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260761 | New WID on Post-quantum Cryptography Migration |
WID new revision of S3-260548 |
Ericsson | Rel-20 |
S3-126 AI: 6.1 |
noted | [WTS] [JSN] | ||
| S3-260762 | New SID on Security of application user consent architecture |
SID new revision of S3-260691 |
Ericsson, Interdigital | Rel-20 |
S3-126 AI: 6.1 |
noted | [WTS] [JSN] | ||
| S3-260763 | Revised SID for AIoT security ph2 | SID revised | OPPO | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 6.3 |
withdrawn | [WTS] [JSN] | |
| S3-260764 | Draft TR 33.786 | draft TR | Motorola Mobility | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
approved | [WTS] [JSN] | |
| S3-260765 | Updates to Solution#1 |
pCR revision of S3-260240 |
Lenovo, Motorola Mobility | 33.786 0.3.0 | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
approved | [WTS] [JSN] |
| S3-260766 | Updates to Solution#4 |
pCR revision of S3-260241 |
Lenovo, Motorola Mobility | 33.786 0.3.0 | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
approved | [WTS] [JSN] |
| S3-260767 | Resolving the ENs on Solution #2 |
pCR revision of S3-260467 |
Huawei, HiSilicon | 33.786 0.3.0 | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
approved | [WTS] [JSN] |
| S3-260768 | Resolving ENs in solution#5 |
pCR revision of S3-260534 |
Samsung | 33.786 0.3.0 | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
approved | [WTS] [JSN] |
| S3-260769 | Resolving ENs and evaluation of solution#3 |
pCR revision of S3-260693 |
Ericsson | 33.786 0.3.0 | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
approved | [WTS] [JSN] |
| S3-260770 | Conclusion for KI#1 and KI#2 |
pCR revision of S3-260535 |
Samsung | 33.786 0.3.0 | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
approved | [WTS] [JSN] |
| S3-260771 | Cover sheet TR 33.786 for information | TS or TR cover | Motorola Mobility | FS_AIMLE_SEC | Rel-20 |
S3-126 AI: 5.2.3 |
approved | [WTS] [JSN] | |
| S3-260772 | Reply LS on MANET multicast support |
LS out LS is reply to S3-260121 source LS: S2-2511306 LS To: SA2 revision of S3-260409 |
SA3 | 5G_ProSe_Sec_Ph3 | Rel-20 |
S3-126 AI: 3 |
approved | [WTS] [JSN] | |
| S3-260773 | Add conclusions for Key Issues #1 and #2 |
pCR revision of S3-260256 |
InterDigital, Europe, Ltd. | 33.785 0.3.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-126 AI: 5.2.6 |
approved | [WTS] [JSN] |
| S3-260774 | Clean Up for TR 33.785 |
pCR revision of S3-260211 |
vivo | 33.785 0.3.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-126 AI: 5.2.6 |
approved | [WTS] [JSN] |
| S3-260775 | Draft TR 33.785 | draft TR | Vivo | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-126 AI: 5.2.6 |
approved | [WTS] [JSN] | |
| S3-260776 | Cover sheet TR 33.785 for approval | TS or TR cover | Interdigital | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-126 AI: 5.2.6 |
approved | [WTS] [JSN] | |
| S3-260777 | Draft TS 33.502 | draft TS | Vodafone | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
approved | [WTS] [JSN] | |
| S3-260778 | pCR to TS 33.502 – Detecting SBA layer parameters change |
pCR revision of S3-260157 |
Vodafone, Verizon, China Mobile, NTT DOCOMO, KDDI, AT&T, Deutsche Telekom, Telecom Italia | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-260779 | pCR to TS 33.502 – Detecting events related to unexpected communication model flows |
pCR revision of S3-260228 |
Vodafone, Verizon, China Mobile, NTT DOCOMO, KDDI, AT&T, Deutsche Telekom, Telecom Italia | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-260780 | pCR to TS 33.502 – Removal of ENs |
pCR revision of S3-260158 |
Vodafone, Verizon, China Mobile, NTT DOCOMO, KDDI, AT&T, Deutsche Telekom, Telecom Italia | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-260781 | Event instance identifier and clarification of event number/event code |
pCR revision of S3-260617 |
Ericsson, Vodafone | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-260782 | Clarification of the security event related to massive number of incoming messages |
pCR revision of S3-260618 |
Ericsson | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-260783 | Update to Overview of Security related Events Handling |
pCR revision of S3-260459 |
Huawei, HiSilicon | 33.502 1.0.0 | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-260784 | Draft TR 33.700-23 | draft TR | China Telecom | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
approved | [WTS] [JSN] | |
| S3-260785 | Resolve EN and add evaluation to solution #2 |
pCR revision of S3-260317 |
ZTE Corporation | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-260786 | Updating solution#4 and add evaluation |
pCR revision of S3-260364 |
China Telecommunications | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-260787 | Update solution #3 of TR 33.700-23 |
pCR revision of S3-260482 |
Xiaomi Communications | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-260788 | [TR 33.700-23] Resolving ENs in solution#5 |
pCR revision of S3-260532 |
Samsung | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-260789 | pCR on evaluation of Sol#6 |
pCR revision of S3-260439 |
Nokia | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-260790 | Update solution #8 of TR 33.700-23 |
pCR revision of S3-260483 |
Xiaomi Communications | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-260791 | Resolving Editors’ Note in Solution-7 Open Discover Service APIs |
pCR revision of S3-260637 |
Ericsson | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-260792 | Update solution #10 of TR 33.700-23 |
pCR revision of S3-260484 |
Xiaomi Communications | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-260793 | Resolving Editors’ Note in Solution-9 Scope Parameter with Purpose Information |
pCR revision of S3-260638 |
Ericsson | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-260794 | Update to KI#4 Credentials Unavailability |
pCR revision of S3-260639 |
Ericsson | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-260795 | LS on Security Requirements for 6G Roaming |
LS out LS To: GSMA NRG,GSMA FASG revision of S3-260448 |
SA3 | Rel-20 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] | ||
| S3-260796 | Pseudo-CR on MAC-CE risk analysis skeleton |
pCR revision of S3-260282 |
Ericsson | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-260797 | Way forward for MAC CE security including pCR |
pCR revision of S3-260715 |
NTT DOCOMO INC.. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-260798 | AnnexB - proposal for a new annex content for B.2 on MAC CE methodology and risk analysis | pCR | Huawei, HiSilicon | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
withdrawn | [WTS] [JSN] |
| S3-260799 | Annex B MAC-CE risk analysis |
pCR revision of S3-260299 |
Nokia, Samsung, ZTE, OPPO | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-260800 | Draft TR 33.801-01 | draft TR | ORANGE | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] | |
| S3-260801 | LS on questions on MAC-CE security |
LS out LS To: RAN2 |
SA3 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] | |||
| S3-260802 | SA#2 – KI#NEW - MAC CE security |
pCR revision of S3-260610 |
Qualcomm Incorporated | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-260803 | Update on Snow5G 256-bit Specification |
CR revision of S3-260156 |
Nokia | 35.240 18.0.0 CR#12 catF | 256_Algo, TEI20 | Rel-20 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260804 | Update on AES 256-bit Specification |
CR revision of S3-260145 |
Nokia | 35.243 18.0.0 CR#11 catF | 256_Algo, TEI20 | Rel-20 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260805 | Update on ZUC 256-bit Specification |
CR revision of S3-260148 |
Nokia | 35.246 19.0.0 CR#21 catF | 256_Algo, TEI20 | Rel-20 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260806 | Update on ZUC 256-bit Design Conformance Test Data |
CR revision of S3-260150 |
Nokia | 35.248 18.0.0 CR#11 catF | 256_Algo, TEI20 | Rel-20 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260807 | Solution for Hybrid PQC based SUCI Computation |
pCR revision of S3-260249 |
Lenovo, Motorola Mobility | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260808 | SA#2 - KI#NEW - System Information protection/paging protection |
pCR revision of S3-260537 |
Samsung, SK Telecom | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260809 | SA#2 – KI#NEW - Security of initial RAN messages prior to AS security activation |
pCR revision of S3-260245 |
InterDigital, Inc. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260810 | New Key Issue for SA#2 on Security Enhancement for RAN Mobility |
pCR revision of S3-260505 |
Xiaomi EV Technology | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-260811 | Corrections for TR 33.703 |
pCR revision of S3-260347 |
Huawei, HiSilicon | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260812 | Clause 4.1 - Add missing description of SA#4 |
pCR revision of S3-260444 |
Orange (Rapporteur) | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-260813 | Draft TR 33.714 | draft TR | OPPO | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] | |
| S3-260814 | Update R20 AIOT security scope |
pCR revision of S3-260456 |
OPPO | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260815 | KI#2: solution for DO-A capable AIoT devices |
pCR revision of S3-260568 |
Thales, ZTE | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260816 | New solution on authentication |
pCR revision of S3-260273 |
OPPO | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260817 | New solution on authentication of DO-A capable device |
pCR revision of S3-260493 |
Beijing Xiaomi Mobile Software | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260818 | New solution to KI#2: AKA-based authentication for inventory, command and registration |
pCR revision of S3-260631 |
Ericsson | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260819 | New sol on AIoT authentication |
pCR revision of S3-260547 |
Samsung | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260820 | New solution on DO-A capable AIoT Device registration procedure |
pCR revision of S3-260570 |
CATT | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260821 | Authentication procedure for DO-A capable AIoT devices |
pCR revision of S3-260598 |
Qualcomm Incorporated | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260822 | Solution Update |
pCR revision of S3-260274 |
OPPO | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260823 | update to solution#2 |
pCR revision of S3-260375 |
Huawei, HiSilicon | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260824 | New solution on DO-A capable AIoT Device communication protection |
pCR revision of S3-260569 |
CATT | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260825 | Solution to KI#4 concerning privacy protection of DOA message |
pCR revision of S3-260294 |
Nokia | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260826 | new solution on ID privacy protection |
pCR revision of S3-260376 |
Huawei, HiSilicon | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260827 | New solution on T-ID based AIOT device privacy protection |
pCR revision of S3-260369 |
OPPO | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260828 | Addressing EN in Solution #6 for group paging using Bloom filter |
pCR revision of S3-260642 |
Ericsson | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260829 | New solution for UE Authorization during Intermediate UE selection |
pCR revision of S3-260492 |
Beijing Xiaomi Mobile Software | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260830 | New solution on authorization of intermediate UE for 5G Ambient IoT |
pCR revision of S3-260721 |
OPPO | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260831 | Draft TR33.700-30 | draft TR | Qualcomm | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
approved | [WTS] [JSN] | |
| S3-260832 | New Solution for KI#1 Secure NAS messages via one pair of COUNTs |
pCR revision of S3-260398 |
Huawei, HiSilicon | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-260833 | Living doc to TS 33.216 | draftCR | Huawei, HiSilicon,BSI (DE),Ericsson | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260834 | New solution to the NAS key stream re-use issue during S&F operations |
pCR revision of S3-260601 |
Qualcomm Incorporated | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-260835 | Address ENs in Sol#6 of TR 33.700-30 |
pCR revision of S3-260470 |
Huawei, HiSilicon | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-260836 | Draft TR 33.724 | draft TR | China Telecom | FS_5G_WAB_SEC | Rel-20 |
S3-126 AI: 5.2.14 |
approved | [WTS] [JSN] | |
| S3-260837 | Pesudo-CR on New Solution for KI#1 |
pCR revision of S3-260577 |
Ericsson | 33.724 0.2.0 | FS_5G_WAB_SEC | Rel-20 |
S3-126 AI: 5.2.14 |
approved | [WTS] [JSN] |
| S3-260838 | Solution for KI #2 |
pCR revision of S3-260472 |
Huawei, HiSilicon | 33.724 0.2.0 | FS_5G_WAB_SEC | Rel-20 |
S3-126 AI: 5.2.14 |
approved | [WTS] [JSN] |
| S3-260839 | Pseudo-CR on Resolving editor's notes for RFC 9700 best practices |
pCR revision of S3-260670 |
Ericsson,Nokia | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-260840 | Draft TR 33.755 | draft TR | Huawei | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
approved | [WTS] [JSN] | |
| S3-260841 | Replay prevention |
pCR revision of S3-260739 |
Nokia | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-260842 | Resolution for EN for RFC 8725 |
pCR revision of S3-260402 |
Huawei, HiSilicon,Ericsson,Nokia | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-260843 | New solution for SUCI calculation with symmetric key |
pCR revision of S3-260264 |
InterDigital, Inc. | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260844 | EN addressing and evaluation for solution#4 |
pCR revision of S3-260390 |
Huawei, HiSilicon | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260845 | Pseudo-CR on Best security practice on using end-to-end TLS between the client and the resource server |
pCR revision of S3-260672 |
Ericsson | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-260846 | Pseudo-CR on Best security practice on transmission of authorization responses | pCR | Ericsson | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
withdrawn | [WTS] [JSN] |
| S3-260847 | Pseudo-CR on Best security practice on sender-constrained access tokens |
pCR revision of S3-260675 |
Ericsson | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
noted | [WTS] [JSN] |
| S3-260848 | Scope |
pCR revision of S3-260744 |
Nokia | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-260849 | Overview |
pCR revision of S3-260746 |
Nokia | 33.755 0.2.0 | GROUPE, FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-260850 | Draft TR 33.704 | draft TR | China Mobile | FS_SCP | Rel-20 |
S3-126 AI: 5.2.15 |
approved | [WTS] [JSN] | |
| S3-260851 | skeleton of security configuration provisioning |
draft TR revision of S3-260582 |
China Mobile | FS_SCP | Rel-20 |
S3-126 AI: 5.2.15 |
approved | [WTS] [JSN] | |
| S3-260852 | pcr on scope for security configuration provisioning |
pCR revision of S3-260583 |
China Mobile | 33.704 0.0.0 | FS_SCP | Rel-20 |
S3-126 AI: 5.2.15 |
approved | [WTS] [JSN] |
| S3-260853 | Update the conclusion of KI#1 |
pCR revision of S3-260411 |
Huawei, HiSilicon | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260854 | Conclusion for KI #2 in TR 33.777 |
pCR revision of S3-260728 |
OPPO | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260855 | Conclusion for KI#3 |
pCR revision of S3-260308 |
ZTE Corporation | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260856 | Update to Key Issue #4 |
pCR revision of S3-260500 |
Xiaomi EV Technology | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260857 | Conclude to the Key Issues of signal attacks |
pCR revision of S3-260414 |
Huawei, HiSilicon | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260858 | Update to Key Issue #5 |
pCR revision of S3-260501 |
Xiaomi EV Technology | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260859 | A hybrid scheme for SUPI protection |
pCR revision of S3-260696 |
China Mobile Com. Corporation | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260860 | New SID on Mission Critical Next Generation Security |
SID new revision of S3-260263 |
Motorola Solutions UK Ltd. | Rel-20 |
S3-126 AI: 6.2 |
agreed | [WTS] [JSN] | ||
| S3-260861 | SA#3-update-update SA#3 description -update to the security area on UE to Core Network Security |
pCR revision of S3-260383 |
Huawei, HiSilicon | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-260862 | Updating Sol #3 for SUCI calculation |
pCR revision of S3-260350 |
Huawei, HiSilicon | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260863 | SA#6 - Update - addition of SA6 reference |
pCR revision of S3-260556 |
Nokia | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-260864 | New Security Area on Data collection for security monitoring |
pCR revision of S3-260624 |
Ericsson, AT&T, Lenovo, Motorola Mobility, NSA, T-Mobile US, Nokia, SK Telecom, Deutsche Telekom | 33.801-01 5.3.1 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-260865 | SA#NEW- AI Security |
pCR revision of S3-260745 |
Nokia | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260866 | SA#NEW Security and Privacy of Data Framework |
pCR revision of S3-260213 |
vivo, InterDigital, OPPO, China Mobile, Apple, CATT, Samsung, SKT | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260867 | SA#1 - Security Assumptions - Add security assumptions for a serving network security anchor |
pCR revision of S3-260625 |
Ericsson | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-260868 | SA#1 – KI#NEW - Security Domains and Trust Anchors |
pCR revision of S3-260253 |
InterDigital, Inc. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-260869 | SA#1 – KI#NEW - 6G Key Hierarchy and Key Lifecycle Management |
pCR revision of S3-260254 |
InterDigital, Inc. | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-260870 | Corrections to the Nadm_SecTID_Get service operation and out of sync detection |
CR revision of S3-260222 |
Lenovo | 33.369 19.1.0 CR#741 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 3 |
agreed | [WTS] [JSN] |
| S3-260871 | Reply to LS on Out of sync T-ID handling for AIoT |
LS out LS is reply to S3-260108 source LS: C4-255429 LS To: CT4 revision of S3-260236 |
SA3 | Rel-19 |
S3-126 AI: 3 |
approved | [WTS] [JSN] | ||
| S3-260872 | Pseudo-CR on defining terms for TR 33.771 |
pCR revision of S3-260594 |
Qualcomm Incorporated | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260873 | Draft TR 33.771 | draft TR | Vivo | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] | |
| S3-260874 | Introduction of user scenarios for 256-bit support |
pCR revision of S3-260181 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-260875 | Update on A.3 Order of Operations |
pCR revision of S3-260220 |
vivo | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260876 | Pseudo-CR on assumption update |
pCR revision of S3-260193 |
KDDI | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260877 | New KI on authenticated encryption |
pCR revision of S3-260686 |
Ericsson | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260878 | AEAD - KI#1 revision |
pCR revision of S3-260514 |
Apple | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260879 | Pseudo-CR on solution for supporting AEAD mode |
pCR revision of S3-260595 |
Qualcomm Incorporated | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260880 | New solution on algorithm selection |
pCR revision of S3-260269 |
OPPO | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260881 | New solutiion on AEAD Algorithm Interface |
pCR revision of S3-260219 |
vivo | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260882 | New solution on using NCAx as pure cipher algorithm |
pCR revision of S3-260270 |
OPPO | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260883 | New solution on using NCAx as pure integrity algorithm |
pCR revision of S3-260272 |
OPPO | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260884 | New solution about on-demand Extra-IV value derivation |
pCR revision of S3-260394 |
Huawei, HiSilicon | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260885 | New sol on using NCAx as cipher and integrity algorithm |
pCR revision of S3-260590 |
OPPO | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260886 | New Solution for KI#2 |
pCR revision of S3-260690 |
Ericsson | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260887 | Solution to KI#3 |
pCR revision of S3-260699 |
Lenovo, Motorola Mobility | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260888 | Solution enhancements for solution 1 |
pCR revision of S3-260180 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260889 | Solution evaluation for solution 1 |
pCR revision of S3-260177 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260890 | Solution#4 Update on AEAD Algorithm Negotiation |
pCR revision of S3-260218 |
vivo | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260891 | resolve EN and add evaluation for solution #3 |
pCR revision of S3-260333 |
ZTE Corporation | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260892 | update to solution#5 |
pCR revision of S3-260379 |
Huawei, HiSilicon | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260893 | Address the ENs in solution #6 |
pCR revision of S3-260494 |
Beijing Xiaomi Mobile Software | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260894 | Add the evaluation of solution #6 |
pCR revision of S3-260495 |
Beijing Xiaomi Mobile Software | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260895 | Solution evaluation for solution 7 |
pCR revision of S3-260179 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260896 | update to solution#9 |
pCR revision of S3-260380 |
Huawei, HiSilicon | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-260897 | Draft TR 33.703 | draft TR | Huawei | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] | |
| S3-260898 | Considerations for TLS 1.3 |
pCR revision of S3-260164 |
AT&T Services, Inc. | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260899 | hybrid KEM based SUCI calculation |
pCR revision of S3-260306 |
ZTE Corporation | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260900 | Pseudo-CR on ECIES-MLKEM Hybrid SUCI Calculation |
pCR revision of S3-260602 |
Qualcomm Incorporated | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260901 | Pseudo-CR on ECKEM-MLKEM Hybrid SUCI Calculation |
pCR revision of S3-260603 |
Qualcomm Incorporated | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260902 | Pseudo-CR on Backward Compatible Hybrid SUCI Calculation |
pCR revision of S3-260604 |
Qualcomm Incorporated | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260903 | Solving the Editors Notes Solution 2 |
pCR revision of S3-260176 |
Nokia | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260904 | Evaluation of solution #5 |
pCR revision of S3-260560 |
Thales, ORANGE, Samsung, NCSC | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260905 | Evaluation of solution #6 |
pCR revision of S3-260561 |
Thales, ORANGE, Samsung, NCSC | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260906 | Addressing Editor’s Notes and adding Evaluation to Solution #7 |
pCR revision of S3-260550 |
Ericsson | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260907 | pCR to evaluation for solution #8 |
pCR revision of S3-260522 |
Samsung, Lenovo | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260908 | pCR to evaluation for solution #9 |
pCR revision of S3-260523 |
Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260909 | pCR to update solution #10 |
pCR revision of S3-260519 |
Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260910 | pCR to evaluation for solution #11 |
pCR revision of S3-260527 |
Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260911 | Evaluation to Solution #11 |
pCR revision of S3-260549 |
Ericsson, Thales, Orange | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260912 | Solving the Editors Notes in Solution 12 |
pCR revision of S3-260169 |
Nokia | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260913 | Evaluation on the hybrid SUCI |
pCR revision of S3-260174 |
Nokia | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260914 | pCR to evaluation for solution #13 |
pCR revision of S3-260525 |
Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260915 | Solution update on solution#14 |
pCR revision of S3-260210 |
vivo | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260916 | Pseudo-CR on MIKEY-SAKKE PQC evaluation |
pCR revision of S3-260720 |
Motorola Solutions UK Ltd. | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260917 | Conclusions for IKEv2 |
pCR revision of S3-260683 |
China Mobile Com. Corporation | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260918 | Overall evaluation for SUCI solutions |
pCR revision of S3-260348 |
Huawei, HiSilicon | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-260919 | Draft TR 33.746 | draft TR | ZTE | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
approved | [WTS] [JSN] | |
| S3-260920 | Updates to Key Issue#1 |
pCR revision of S3-260360 |
Nokia, Samsung | 33.746 0.3.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
approved | [WTS] [JSN] |
| S3-260921 | New sol on security protection for N2 interface for NR Femto |
draftCR revision of S3-260356 |
China Telecommunications Corp. | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
approved | [WTS] [JSN] | |
| S3-260922 | New sol on security protection for N3 and N9 interface for NR Femto system |
draftCR revision of S3-260357 |
China Telecommunications Corp. | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
approved | [WTS] [JSN] | |
| S3-260923 | New Solution for Key Issue #4 |
pCR revision of S3-260562 |
Nokia | 33.746 0.3.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
approved | [WTS] [JSN] |
| S3-260924 | Conclusions for KI#1 |
pCR revision of S3-260323 |
ZTE Corporation | 33.746 0.3.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
approved | [WTS] [JSN] |
| S3-260925 | Conclusions for KI#2 |
pCR revision of S3-260324 |
ZTE Corporation | 33.746 0.3.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
approved | [WTS] [JSN] |
| S3-260926 | Conclusions for KI#3 |
pCR revision of S3-260325 |
ZTE Corporation | 33.746 0.3.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
approved | [WTS] [JSN] |
| S3-260927 | Conclusions for KI#4 |
pCR revision of S3-260326 |
ZTE Corporation | 33.746 0.3.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.13 |
approved | [WTS] [JSN] |
| S3-260928 | New solution on NAS keys isolation in S&F operations |
pCR revision of S3-260581 |
CATT | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-260929 | Update SA#5 Add new security aspects |
pCR revision of S3-260558 |
CATT | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-260930 | Pseudo-CR on 33.511 gNB SCAS - Key Refresh |
other revision of S3-260223 |
NPL | SCAS_5GA | Rel-19 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260931 | Living document to TS 33.511 |
draftCR revision of S3-260419 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260932 | Living document to TS 33.512 |
draftCR revision of S3-260420 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260933 | Add reference terms update test cases and add new test case of NAS protection of Initial NAS message | CR | Huawei, HiSilicon | 33.512 19.0.0 CR#50 catB | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
agreed | [WTS] [JSN] |
| S3-260934 | Living document to TS 33.517 | draftCR | Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260935 | Correct NRF test case for access token request verification |
other revision of S3-260478 |
Ericsson | SCAS_5GA |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | ||
| S3-260936 | Add new AEF test case that verifies whether revocation of an access token in an RNAA enabled CAPIF deployment is correctly implemented |
other revision of S3-260708 |
BSI (DE), Montsecure, Rakuten Mobile Inc. | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] | |
| S3-260937 | Living document to TS 33.518 |
draftCR revision of S3-260424 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260938 | Add new test cases on Indirect Communication and token verification | CR | Huawei, HiSilicon | 33.518 19.0.0 CR#11 catB | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
agreed | [WTS] [JSN] |
| S3-260939 | Living document to TS 33.521 |
draftCR revision of S3-260426 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260940 | Cover sheet TS 33.547 for information | TS or TR cover | CATT | SCAS_Femto_SeGW | Rel-20 |
S3-126 AI: 5.1.6 |
approved | [WTS] [JSN] | |
| S3-260941 | Add new CAPIF CF test case that verifies whether the onboard credential is correctly validated |
other revision of S3-260707 |
BSI (DE), Montsecure, Rakuten Mobile Inc. | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] | |
| S3-260942 | Addressing key updating EN in sol#4 and updating evaluation |
pCR revision of S3-260395 |
Huawei, HiSilicon | 33.778 0.2.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-126 AI: 5.2.5 |
approved | [WTS] [JSN] |
| S3-260943 | Draft TR 33.778 | draft TR | Huawei | FS_PSK_MQC_TLS | Rel-20 |
S3-126 AI: 5.2.5 |
approved | [WTS] [JSN] | |
| S3-260944 | Addressing roaming EN in sol#5 and updating evaluation |
pCR revision of S3-260417 |
Huawei, HiSilicon | 33.778 0.2.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-126 AI: 5.2.5 |
approved | [WTS] [JSN] |
| S3-260945 | Resolution of Editor’s Note in Solution #3 |
pCR revision of S3-260499 |
Xiaomi EV Technology | 33.778 0.2.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-126 AI: 5.2.5 |
approved | [WTS] [JSN] |
| S3-260946 | Draft TR 33.758 | draft TR | China Telecom | FS_PLMNNPN_Ph2 | Rel-20 |
S3-126 AI: 5.2.4 |
approved | [WTS] [JSN] | |
| S3-260947 | Update the clause 5 Security assumptions |
pCR revision of S3-260166 |
Johns Hopkins University APL | 33.758 0.1.0 | FS_PLMNNPN_Ph2 | Rel-20 |
S3-126 AI: 5.2.4 |
approved | [WTS] [JSN] |
| S3-260948 | Remove the EN in clause 4 to 6 |
pCR revision of S3-260318 |
ZTE Corporation | 33.758 0.1.0 | FS_PLMNNPN_Ph2 | Rel-20 |
S3-126 AI: 5.2.4 |
approved | [WTS] [JSN] |
| S3-260949 | Security requirements for KI#1 |
pCR revision of S3-260335 |
China Telecommunications Corp.,, ZTE, Nokia | 33.758 0.1.0 | FS_PLMNNPN_Ph2 | Rel-20 |
S3-126 AI: 5.2.4 |
noted | [WTS] [JSN] |
| S3-260950 | Solution to inter domain security on N9 interface |
pCR revision of S3-260337 |
China Telecommunications Corp., ZTE | 33.758 0.1.0 | FS_PLMNNPN_Ph2 | Rel-20 |
S3-126 AI: 5.2.4 |
approved | [WTS] [JSN] |
| S3-260951 | Sol7 update |
pCR revision of S3-260370 |
Ericsson | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-260952 | Draft TR 33.777 | draft TR | Xiaomi | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
approved | [WTS] [JSN] | |
| S3-260953 | Update requirement and test case of clause 4.2.1.2.6 and add protocols to the robustness and fuzz testing | CR | Huawei, HiSilicon | 33.521 19.0.0 CR#6 catF | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
agreed | [WTS] [JSN] |
| S3-260954 | pCR on TS 33.117 protection against brute force and dict. attacks |
other revision of S3-260650 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260955 | pCR on TS 33.117 protection of transport layer |
other revision of S3-260652 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260956 | Living document to TS 33.117 |
draftCR revision of S3-260429 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260957 | Update terms requirement and test cases to several test cases. | CR | Huawei, HiSilicon | 33.117 19.2.0 CR#230 catB | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
agreed | [WTS] [JSN] |
| S3-260958 | Correction of 33.515 TC_CHARGING_ID_UNIQUENESS_SMF pre-conditions |
draftCR revision of S3-260655 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260959 | Update test cases and add abbreviations to TS 33.513 | CR | Huawei, HiSilicon | 33.513 19.0.0 CR#16 catF | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
agreed | [WTS] [JSN] |
| S3-260960 | Update references and execution steps to TS 33.514 | CR | Huawei, HiSilicon | 33.514 19.1.0 CR#35 catF | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
agreed | [WTS] [JSN] |
| S3-260961 | Add TLS to the robustness and fuzz testing to TS 33.519 | CR | Huawei, HiSilicon | 33.519 19.0.0 CR#7 catF | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
agreed | [WTS] [JSN] |
| S3-260962 | Living document to TR 33.926 |
draftCR revision of S3-260427 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260963 | Update threat category impact interface and new threat to eNB, NRF and NSSAAF to TS 33.926 | CR | Huawei, HiSilicon | 33.926 19.4.0 CR#110 catB | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
agreed | [WTS] [JSN] |
| S3-260964 | Add abbreviations update execution steps to TS 33.116 | CR | Huawei, HiSilicon | 33.116 19.0.0 CR#6 catF | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
agreed | [WTS] [JSN] |
| S3-260965 | Format and references corrections to TS 33.523 | CR | BSI (DE) | 33.523 19.2.0 CR#13 catF | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
agreed | [WTS] [JSN] |
| S3-260966 | Update Test Names to TS 33.226 | CR | BSI (DE), Montsecure, Deutsche Telekom | 33.226 19.0.0 CR#2 catF | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
agreed | [WTS] [JSN] |
| S3-260967 | Update Threat References: and test cases to TS 33.216 | CR | Huawei, HiSilicon,BSI (DE),Ericsson | 33.216 19.1.0 CR#36 catB | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
agreed | [WTS] [JSN] |
| S3-260968 | Update Solution#2.2 |
pCR revision of S3-260410 |
Huawei, HiSilicon | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-260969 | Solution for KI#2 |
pCR revision of S3-260440 |
Ericsson | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-260970 | Skeleton for TS 33.531(SCAS for CAPIF CF) |
draft TS revision of S3-260278 |
Rakuten Mobile, Inc, BSI (DE) | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] | |
| S3-260971 | Draft TS 33.531 | draft TS | Rakuten Mobile | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] | |
| S3-260972 | Add new CAPIF CF test case that verifies whether AEF_PSK is computed correctly by the CAPIF CF |
other revision of S3-260706 |
BSI (DE), Montsecure, Rakuten Mobile Inc. | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] | |
| S3-260973 | Add new API Exposing Function test case that verifies whether the API Exposing Function correctly validates the resOwnerId claim when Resource owner-aware Northbound API Access is used |
other revision of S3-260709 |
BSI (DE), Montsecure, Rakuten Mobile Inc. | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] | |
| S3-260974 | New solution for TR 33.777 KI#3 | pCR | Xiaomi Communications | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
withdrawn | [WTS] [JSN] |
| S3-260975 | 6G SID-working procedures and priorities for the next meeting | other | ORANGE (Rapporteur) |
S3-126 AI: 5.3.1 |
noted | [WTS] [JSN] | |||
| S3-260976 | Correction of the Nadm_SecAuthentication_Get service operation |
CR revision of S3-260225 |
Lenovo | 33.369 19.1.0 CR#761 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260977 | Update to the length of security parameters |
CR revision of S3-260374 |
Huawei, HiSilicon | 33.369 19.1.0 CR#871 catF | AmbientIoT-SEC | Rel-19 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260978 | Correction of misalignment with TS 29.510: Replace appended PLMN ID access token claims with PLMN ID specific claims in roaming | CR | Ericsson,Nokia | 33.501 19.5.0 CR#2222 catF | TEI19 | Rel-19 |
S3-126 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-260979 | [TR 33.700-23] Conclusion for key issue#1 |
pCR revision of S3-260533 |
Samsung | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-260980 | Protection of information for DO-A capable AIoT devices |
pCR revision of S3-260599 |
Qualcomm Incorporated | 33.714 0.2.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-126 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-260981 | Adding scope |
pCR revision of S3-260600 |
Qualcomm Incorporated | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-260982 | Resolve EN in solution #1 |
pCR revision of S3-260315 |
ZTE Corporation | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-260983 | Resolve EN in solution #2 |
pCR revision of S3-260316 |
ZTE Corporation | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-260984 | Address the EN in solution #5 |
pCR revision of S3-260489 |
Beijing Xiaomi Mobile Software | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-260985 | Add the evaluation of solution #5 |
pCR revision of S3-260490 |
Beijing Xiaomi Mobile Software | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-260986 | EN removal and evaluation for solution #7 |
pCR revision of S3-260700 |
Nokia | 33.700-30 0.2.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-260987 | pCR on TR 33.730 completion of trusted image repo test case |
other revision of S3-260660 |
BSI (DE) | FS_SCAS_CP | Rel-20 |
S3-126 AI: 5.2.8 |
approved | [WTS] [JSN] | |
| S3-260988 | pCR on TR 33.730 completion of vulnerability scanning or containerized NF |
other revision of S3-260661 |
BSI (DE) | FS_SCAS_CP | Rel-20 |
S3-126 AI: 5.2.8 |
approved | [WTS] [JSN] | |
| S3-260989 | pCR on TR 33.730 completion of Containerized NF run-time security |
other revision of S3-260662 |
BSI (DE) | FS_SCAS_CP | Rel-20 |
S3-126 AI: 5.2.8 |
approved | [WTS] [JSN] | |
| S3-260990 | pCR on TR 33.730 new test on Resource quotas and limits enforcement |
other revision of S3-260664 |
BSI (DE) | FS_SCAS_CP | Rel-20 |
S3-126 AI: 5.2.8 |
approved | [WTS] [JSN] | |
| S3-260991 | Corrections and updated test cases | CR | Huawei | 33.511 19.3.0 CR#95 catF | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
agreed | [WTS] [JSN] |
| S3-260992 | Update references test names based on NESASG comments in TS 33.511 | CR | Huawei | 33.517 19.0.0 CR#15 catF | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
agreed | [WTS] [JSN] |
| S3-260993 | Correction of 33.515 TC_CHARGING_ID_UNIQUENESS_SMF pre-conditions | CR | Huawei | 33.515 19.0.0 CR#14 catF | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
agreed | [WTS] [JSN] |
| S3-260994 | Update preconditions to clause 4.2.2.1.4 in TS 33.515 | CR | Huawei | 33.515 19.0.0 CR#15 catF | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
agreed | [WTS] [JSN] |
| S3-260995 | Cover sheet TR 33.531 for information | TS or TR cover | Rakuten Mobile | SCAS_5GA_CAPIF | Rel-20 |
S3-126 AI: 5.1.7 |
approved | [WTS] [JSN] | |
| S3-260996 | pCR on adding different utilizations of containers for containerized network products |
pCR revision of S3-260465 |
Huawei, HiSilicon | 33.730 1.0.0 | FS_SCAS_CP | Rel-20 |
S3-126 AI: 5.2.8 |
approved | [WTS] [JSN] |
| S3-260997 | pCR on TS 33.117 security event logging |
other revision of S3-260653 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260998 | pCR on TS 33.117 for TC_NO_UNUSED_HTTP_METHODS |
other revision of S3-260654 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-126 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-260999 | pCR to evaluation for solution #14 |
pCR revision of S3-260526 |
Samsung | 33.703 0.3.0 | FS_CryptoPQC | Rel-20 |
S3-126 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-261000 | Conclusion for 33.730 |
pCR revision of S3-260454 |
Ericsson | 33.730 1.0.0 | FS_SCAS_CP | Rel-20 |
S3-126 AI: 5.2.8 |
approved | [WTS] [JSN] |
| S3-261001 | pCR on resolution of ENs and conclusion for Sol#11 |
pCR revision of S3-260442 |
Nokia | 33.700-23 0.2.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-126 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-261002 | Pseudo-CR on Best security practice on validating all cryptographic operations |
pCR revision of S3-260677 |
Ericsson,Nokia | 33.755 0.2.0 | FS_BSP4SBA | Rel-20 |
S3-126 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-261003 | Draft TR 33.730 | draft TR | Ericsson | FS_SCAS_CP | Rel-20 |
S3-126 AI: 5.2.8 |
approved | [WTS] [JSN] | |
| S3-261004 | Attacker Model update |
pCR revision of S3-260366 |
Nokia | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-261005 | Annex#A - Pseudo-CR providing an Attacker model definition |
pCR revision of S3-260622 |
Ericsson | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-126 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-261006 | Solution evaluation for solution 11 |
pCR revision of S3-260178 |
Nokia | 33.771 0.2.0 | FS_AEAD | Rel-20 |
S3-126 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-261007 | pCR on EN resolution for Solution 1.5 |
pCR revision of S3-260457 |
Nokia | 33.777 0.3.0 | FS_Sensing_SEC | Rel-20 |
S3-126 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-261008 | WID on Security Aspect for NR Femto Phase 2 |
WID new revision of S3-260334 |
ZTE Corporation | Rel-20 |
S3-126 AI: 6.1 |
agreed | [WTS] [JSN] | ||
| S3-261009 | Presentation for Approval to TSG SA - Security related Events Handling |
TS or TR cover revision of S3-260229 |
Vodafone | SECHAND | Rel-20 |
S3-126 AI: 5.1.1 |
approved | [WTS] [JSN] |
910 documents (1.2607209682465 seconds)