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-254000 | Agenda |
agenda revised to S3-254470 |
SA WG3 Chair |
S3-125 AI: 1 |
revised | [WTS] [JSN] | |||
| S3-254001 | Report from SA3#124 | report | MCC |
S3-125 AI: 2.1 |
approved | [WTS] [JSN] | |||
| S3-254002 | Process for SA3#125 | other | SA WG3 Chair |
S3-125 AI: 1 |
noted | [WTS] [JSN] | |||
| S3-254003 | Detailed agenda planning | other | SA WG3 Chair |
S3-125 AI: 1 |
noted | [WTS] [JSN] | |||
| S3-254004 | NESASG Doc 44_006 LS to SA3 re SCAS Improvements | LS in | GSMA |
S3-125 AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-254005 | Reply LS on issues related to support of IMS voice over NB-IoT NTN connected to EPC | LS in | C1-256676 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-254006 | LS on unsupported AIoT commands | LS in | C1-256897 |
S3-125 AI: 3 |
withdrawn | [WTS] [JSN] | |||
| S3-254007 | Reply LS on issues related to support of IMS voice over NB-IoT NTN connected to EPC | LS in | R1-2508096 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-254008 | Reply LS on issues related to support of IMS voice over NB-IoT NTN connected to EPC | LS in | R2-2507784 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-254009 | LS on integrity failure |
LS in LS reply in S3-254709, S3-254136, S3-254225, S3-254491, S3-254547, S3-254709 |
R2-2507915 |
S3-125 AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-254010 | LS on Security parameter in A-IoT paging |
LS in LS reply in S3-254226, S3-254456, S3-254720 |
R2-2507920 |
S3-125 AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-254011 | Reply LS on signalling feasibility of dataset and parameter sharing | LS in | R2-2507929 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-254012 | Reply LS on AIoT Device Permanent ID Length | LS in | R2-2507931 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-254013 | LS on Early Alignment on Access Stratum security aspects |
LS in LS reply in S3-254552, S3-254224, S3-254243, S3-254486, S3-254552 |
R2-2507945 |
S3-125 AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-254014 | Reply LS on “IETF Network Slice Application in 3GPP 5G End-to-End Network Slice” | LS in | R3-257304 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-254015 | Reply LS on Avatar Security Aspects |
LS in LS reply in S3-254551, S3-254551 |
S2-2509593 |
S3-125 AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-254016 | Reply LS on Structure updates of AIoT Identifiers | LS in | S2-2509655 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-254017 | Reply LS on USS changeover procedure | LS in | S2-2509748 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-254018 | Reply LS on specification of dataset and model parameters exchange | LS in | S5-254846 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-254019 | LS on Security parameter in A-IoT paging | LS in | R2-2507920 |
S3-125 AI: 3 |
withdrawn | [WTS] [JSN] | |||
| S3-254020 | Reply LS on USS changeover procedure | LS in | S2-2509748 |
S3-125 AI: 3 |
withdrawn | [WTS] [JSN] | |||
| S3-254021 | Draft TS 33.502 | draft TS | Vodafone | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
approved | [WTS] [JSN] | |
| S3-254022 | CVD-2024-0096 – SNI5GECT: A Practical Approach to Inject aNRchy into 5G NR | LS in | GSMA CVD |
S3-125 AI: 7 |
noted | [WTS] [JSN] | |||
| S3-254023 | LS on control plane CIoT with overhead reduction | LS in | C1-255649 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-254024 | LS on User consent for Data collection at the UE for NW-side model training |
LS in LS reply in S3-254135, S3-254184, S3-254232, S3-254476, S3-254548, S3-254740 |
R2-2506541 |
S3-125 AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-254025 | LS on UE parameters update header security |
LS in LS reply in S3-254550, S3-254550 |
C1-253719 |
S3-125 AI: 3 |
replied to | [WTS] [JSN] | |||
| S3-254026 | LS on handling of inventory and command collision | LS in | C1-256624 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-254027 | Revised WID on mission critical security enhancements for release 20 |
WID revised revision of S3-252353 |
Motorola Solutions Germany | MCX20-SEC | Rel-20 |
S3-125 AI: 6.3 |
endorsed | [WTS] [JSN] | |
| S3-254028 | Security Assurance Specification (SCAS) for the CAPIF Core Function |
WID new revised to S3-254560 |
BSI (DE) | Rel-20 |
S3-125 AI: 6.1 |
revised | [WTS] [JSN] | ||
| S3-254029 | Discussion on SCAS tests for the CAPIF CF work item (WID proposal) | discussion | BSI (DE) | Rel-20 |
S3-125 AI: 6.1 |
noted | [WTS] [JSN] | ||
| S3-254030 | [33.180] Alignment of recording replay user service authorization |
CR revision of S3-253235 |
Airbus | 33.180 19.3.0 CR#2262 catF | MCX20-SEC | Rel-20 |
S3-125 AI: 5.1.2 |
agreed | [WTS] [JSN] |
| S3-254031 | [33.180] Alignment on Logging, Recording, Audit and Discreet Monitoring |
CR revision of S3-253236 |
Airbus, Motorola | 33.180 19.3.0 CR#2272 catB | MCX20-SEC | Rel-20 |
S3-125 AI: 5.1.2 |
agreed | [WTS] [JSN] |
| S3-254032 | TCG progress - report from TCG rapporteur | other | InterDigital Communications |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-254033 | PQC status in TCG | other | InterDigital Communications |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-254034 | Discussion Paper on Security Considerations for MAC Control Elements (MAC CEs) in 6G | discussion | InterDigital Communications |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] | |||
| S3-254035 | LS reply on Early Alignment on Access Stratum security aspects |
LS out LS is reply to S3-254013 source LS: R2-2507945 LS To: RAN2 |
InterDigital Communications |
S3-125 AI: 3 |
merged | [WTS] [JSN] | |||
| S3-254036 | New Security Area on Core Network Security | pCR | Deutsche Telekom AG | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-254037 | New KI on NF Authentication on Application Layer in 6G | pCR | Deutsche Telekom AG | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254038 | Update solution #2 |
pCR revised to S3-254582 |
InterDigital Finland Oy | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
revised | [WTS] [JSN] |
| S3-254039 | New Solution Security for UE-side data collection exposure |
pCR revised to S3-254576 |
InterDigital Finland Oy | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
revised | [WTS] [JSN] |
| S3-254040 | Add conclusion for KI#1 | pCR | InterDigital Finland Oy | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
noted | [WTS] [JSN] |
| S3-254041 | Update solution #1 | pCR | InterDigital Finland Oy | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
approved | [WTS] [JSN] |
| S3-254042 | Conclusion for Key Issue #1 |
pCR revised to S3-254642 |
InterDigital Finland Oy | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
revised | [WTS] [JSN] |
| S3-254043 | [33.180] Error in message structure | CR | Motorola Solutions Germany | 33.180 14.12.0 CR#229 catF | MCSec | Rel-14 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254044 | [33.180] Error in message structure (R15 mirror) | CR | Motorola Solutions, Inc. | 33.180 15.13.0 CR#230 catA | MCSec | Rel-15 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254045 | [33.180] Error in message structure (R16 mirror) | CR | Motorola Solutions, Inc. | 33.180 16.12.0 CR#231 catA | MCSec | Rel-16 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254046 | [33.180] Error in message structure (R17 mirror) | CR | Motorola Solutions, Inc. | 33.180 17.9.0 CR#232 catA | MCSec | Rel-17 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254047 | [33.180] Error in message structure (R18 mirror) | CR | Motorola Solutions, Inc. | 33.180 18.1.0 CR#233 catA | MCSec | Rel-18 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254048 | [33.180] Error in message structure (R19 mirror) | CR | Motorola Solutions, Inc. | 33.180 19.3.0 CR#234 catA | MCSec | Rel-19 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254049 | [33.180] Error in message structure (R20 mirror) | CR | Motorola Solutions, Inc. | 33.180 19.3.0 CR#235 catA | MCSec | Rel-20 |
S3-125 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-254050 | PRINS Refinement on Trust Anchoring |
CR revised to S3-254742 |
BSI (DE) | 33.501 19.4.0 CR#2199 catB | RefinePRINS | Rel-20 |
S3-125 AI: 5.1.4 |
revised | [WTS] [JSN] |
| S3-254051 | Pseudo-CR on Mission Critical PQ options |
pCR revised to S3-254733 |
NCSC, Motorola Solutions, BT, DSIT, NPL | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-254052 | Pseudo-CR on NIST security level recommendations |
pCR revised to S3-254564 |
NCSC, NTAC, BT, BSI, US NSA, NPL, DSIT | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-254053 | Proposed editorial change on the PQC level description | pCR | Nokia | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
noted | [WTS] [JSN] |
| S3-254054 | Details on the KDF | pCR | Nokia | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254055 | Details on how this solution could be used for hybrid PQC | pCR | Nokia | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254056 | Details on why is MAC verification after decryption | pCR | Nokia | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254057 | Details on why replacement of ECIES functional blocks | pCR | Nokia | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254058 | Solution proposal Hybrid SUCI calculation |
pCR revised to S3-254745 |
Nokia | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-254059 | proposed summary of security agencies view | pCR | Nokia | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
merged | [WTS] [JSN] |
| S3-254060 | Solution proposal Symmetric key SUCI |
pCR revised to S3-254746 |
Nokia | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-254061 | Evaluation of Solution | pCR | Nokia | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254062 | Solution proposal AEAD algo selection for NAS and AS |
pCR revised to S3-254661 |
Nokia | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-254063 | introduction of KI on coexistence | pCR | Nokia | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-254064 | Solution proposal AEAD key usage for NAS and AS algorithm |
pCR revised to S3-254667 |
Nokia | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-254065 | Solution proposal Key Hierarchy for NAS and AS AEAD |
pCR revised to S3-254671 |
Nokia | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-254066 | New Key Issue on Key Hierarchy for AS and NAS AEAD | pCR | Nokia | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
merged | [WTS] [JSN] |
| S3-254067 | Discussion on AEAD properties | discussion | Nokia |
S3-125 AI: 5.3.2 |
noted | [WTS] [JSN] | |||
| S3-254068 | New Key Issue on UE specific 256 bit Algo selection | pCR | Nokia | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-254069 | Discussion on the MAC length | discussion | Nokia |
S3-125 AI: 5.3.2 |
noted | [WTS] [JSN] | |||
| S3-254070 | introduction of the KI for MAC length | pCR | Nokia | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-254071 | EN Removal for Solution for NAS COUNT synchronization in store-and-forward operations |
pCR revised to S3-254592 |
Nokia | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-254072 | Evaluation for Solution for NAS COUNT synchronization in store-and-forward operations | pCR | Nokia | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
not treated | [WTS] [JSN] |
| S3-254073 | Solution for Detection of compromised MWAB nodes |
pCR revised to S3-254707 |
Nokia | 33.724 0.1.0 | FS_5G_WAB_SEC | Rel-20 |
S3-125 AI: 5.2.14 |
revised | [WTS] [JSN] |
| S3-254074 | Evaluation for Solution for security of Local UPF for key issue 2 |
pCR revised to S3-254685 |
Nokia | 33.746 0.2.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.13 |
revised | [WTS] [JSN] |
| S3-254075 | EN Removal for Solution for detection of compromised Femto |
pCR revised to S3-254686 |
Nokia | 33.746 0.2.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.13 |
revised | [WTS] [JSN] |
| S3-254076 | pseudo-CR on authorization of sensing service request solution |
pCR revised to S3-254750 |
Nokia, Nokia Shanghai Bell | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-254077 | pseudo-CR on authorization of sensing service request solution | pCR | Nokia, Nokia Shanghai Bell | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
withdrawn | [WTS] [JSN] |
| S3-254078 | pseudo-CR on solution on security of sensing operation | pCR | Nokia, Nokia Shanghai Bell | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-254079 | Pseudo-CR on Solution for purpose of information |
pCR revised to S3-254602 |
Nokia | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-254080 | Pseudo-CR on Solution for Open Discovery Service |
pCR revised to S3-254597 |
Nokia | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-254081 | Pseudo-CR on KI#4 of CAPIF |
pCR revised to S3-254593 |
Nokia | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-254082 | Pseudo-CR on KI#1 update |
pCR revised to S3-254659 |
KDDI Corporation | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-254083 | Pseudo-CR on Conclusion for MPQUIC | pCR | Nokia | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
merged | [WTS] [JSN] |
| S3-254084 | Pseudo-CR on new solution for algorithm selection |
pCR revised to S3-254662 |
KDDI Corporation | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-254085 | Pseudo-CR on new solution for KI#2 interface |
pCR revised to S3-254668 |
KDDI Corporation | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-254086 | Pseudo-CR on ENs resolution for solution 6.6 |
pCR revised to S3-254641 |
Nokia | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
revised | [WTS] [JSN] |
| S3-254087 | FS_AEAD planning | discussion | KDDI Corporation, vivo |
S3-125 AI: 5.3.2 |
noted | [WTS] [JSN] | |||
| S3-254088 | Updating 3GPP Considerations for TLS 1.2 |
pCR revised to S3-254566 |
Ericsson | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-254089 | Updating 3GPP Considerations for TLS 1.3 |
pCR revised to S3-254567 |
Ericsson | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-254090 | Updating 3GPP Considerations for IKEv2 | pCR | Ericsson | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
merged | [WTS] [JSN] |
| S3-254091 | Updating 3GPP Considerations for PKI | pCR | Ericsson | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
merged | [WTS] [JSN] |
| S3-254092 | Updating 3GPP Considerations for JOSE | pCR | Ericsson | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
merged | [WTS] [JSN] |
| S3-254093 | Updating 3GPP Considerations for COSE | pCR | Ericsson | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
merged | [WTS] [JSN] |
| S3-254094 | Addressing Editor’s Notes and adding Evaluation to Solution #7 | pCR | Ericsson | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254095 | Evaluation to Solution #11 | pCR | Ericsson | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254096 | Discussion on solutions for quantum resistant SUCIs | discussion | Ericsson | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] | |
| S3-254097 | Pseudo-CR on Modify TC on image repository | pCR | MITRE-FFRDC | 33.730 0.2.0 | FS_SCAS_CP | Rel-20 |
S3-125 AI: 5.2.8 |
approved | [WTS] [JSN] |
| S3-254098 | Pseudo-CR for 33.518 on New TC on NRF access token request |
other revised to S3-254617 |
MITRE-FFRDC | SCAS_5GA |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | ||
| S3-254099 | Pseudo-CR for 33.926 on new threat on verification of access token request |
other revised to S3-254619 |
MITRE-FFRDC | SCAS_5GA |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | ||
| S3-254100 | Pseudo-CR for 33.117 on Modify TC on security event logging | other | MITRE-FFRDC, BSI (DE) | SCAS_5GA |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | ||
| S3-254101 | Solution for Open Service Discovery |
pCR revised to S3-254598 |
Ericsson | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-254102 | Solution for Group-UE-hosted API invoker authorization |
pCR revised to S3-254594 |
Ericsson | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-254103 | New Solution for more granular authorization based on purpose information |
pCR revised to S3-254600 |
Ericsson | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-254104 | 6G new security area: exposure security |
pCR revised to S3-254654 |
Ericsson | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-254105 | Requirement for AEAD interface |
pCR revised to S3-254660 |
Ericsson | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-254106 | Solution on authorization for ML and FL operations |
pCR revised to S3-254571 |
Ericsson | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
revised | [WTS] [JSN] |
| S3-254107 | A new solution for sensing results exposure via a proxy AF | pCR | InterDigital Washington DC | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-254108 | New Solution for SE sensing authorization policy enforcement | pCR | InterDigital Washington DC | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-254109 | Reply LS on IMS Data Channel | LS in | s3i250674 |
S3-125 AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-254110 | Discussion On Threats from Malicious and Compromised UE | discussion | InterDigital Washington DC | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] | |
| S3-254111 | Lower layer security considerations for 6G Radio | discussion | ST Engineering iDirect |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] | |||
| S3-254112 | Removing EN about LLS in RAN security area | pCR | ST Engineering iDirect | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254113 | pCR to TS 33.502 - Security related Events for Massive Number of Incoming Messages | pCR | IIT Bombay | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
merged | [WTS] [JSN] |
| S3-254114 | pCR to TS 33.502 - Security related Events for Authentication Failure | pCR | IIT Bombay | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
merged | [WTS] [JSN] |
| S3-254115 | pCR to TS 33.502 - Security related Events for replay attacks on the SBA layer | pCR | IIT Bombay | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
merged | [WTS] [JSN] |
| S3-254116 | pCR to TS 33.502 - Security related Events for unexpected SBI call flows | pCR | IIT Bombay | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
noted | [WTS] [JSN] |
| S3-254117 | EN removal for Solution #4 to Key Issue #1 |
pCR revised to S3-254590 |
Sateliot, Novamint | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-254118 | EN removal for Solution #8 to Key Issue #1 | pCR | Sateliot, Novamint | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
not treated | [WTS] [JSN] |
| S3-254119 | pCR to TS 33.502 – Flooding Event |
pCR revised to S3-254677 |
Vodafone, Verizon | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-254120 | pCR to TS 33.502 – Protection for delivery of events |
pCR revised to S3-254680 |
Vodafone, AT&T, China Mobile, T-Mobile USA, Verizon, Telecom Italia, NTT DOCOMO, KDDI, Charter Communications | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-254121 | pCR to TS 33.502 – Protection for configuration of events |
pCR revised to S3-254681 |
Vodafone, T-Mobile US, AT&T, China Mobile, Verizon, Charter Communications, Telecom Italia, KDDI, NTT DOCOMO | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-254122 | pCR to TS 33.502 – Failed Authentication Event | pCR | Vodafone, Verizon, T-Mobile US, China Mobile, NTT DOCOMO, Telecom Italia, AT&T, Charter Communications, KDDI | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
merged | [WTS] [JSN] |
| S3-254123 | Discussion Paper on R2-2507933 LS on Early Alignment on Access Stratum security aspects | discussion | Nokia | Rel-20 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-254124 | pCR to TS 33.502 - Example of trust domain |
pCR revised to S3-254672 |
Vodafone, China Mobile, AT&T, T-Mobile US, Verizon, Charter Communication, KDDI, Telecom Italia | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-254125 | pCR to TS 33.502 - Scope | pCR | Vodafone, Verizon | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-254126 | pCR to TS 33.502 – EN resolving on configuration |
pCR revised to S3-254673 |
Vodafone, Verizon | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-254127 | [draft] Reply LS on User consent for Data collection at the UE for NW-side model training |
LS out LS is reply to S3-254024 source LS: R2-2506541 LS To: RAN2, RAN3 |
NTT DOCOMO INC. | Rel-19 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-254128 | pCR to TS 33.502 – Addressing NOTE on delivery |
pCR revised to S3-254675 |
Vodafone, Verizon | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-254129 | pCR Privacy requirements for sensing |
pCR revised to S3-254614 |
NTT DOCOMO INC. | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-254130 | pCR KI on active attacks |
pCR revised to S3-254615 |
NTT DOCOMO INC. | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-254131 | pCR KI on passive unauthorized sensing |
pCR revised to S3-254616 |
NTT DOCOMO INC. | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-254132 | Replayed messages on SBA layer |
pCR revised to S3-254678 |
Johns Hopkins University APL | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-254133 | Unexpected number of incoming messages | pCR | Johns Hopkins University APL | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
merged | [WTS] [JSN] |
| S3-254134 | Reply LS on Early Alignment on Access Stratum security aspects |
LS out LS To: RAN2 |
ZTE Corporation | FS_6G_Radio | Rel-20 |
S3-125 AI: 3 |
merged | [WTS] [JSN] | |
| S3-254135 | Reply LS on user consent for data collection at the UE for NW-side model training |
LS out LS is reply to S3-254024 LS To: RAN2 |
ZTE Corporation | NR_AIML_air-Core | Rel-19 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |
| S3-254136 | Reply LS on integrity failure |
LS out LS is reply to S3-254009 LS To: RAN2 |
ZTE Corporation | Ambient_IoT_Solutions | Rel-19 |
S3-125 AI: 3 |
merged | [WTS] [JSN] | |
| S3-254137 | Add some abbreviations | CR | ZTE Corporation | 33.369 19.0.0 CR#57 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254138 | update T-ID generation in annex B |
CR revised to S3-254726 |
ZTE | 33.369 19.0.0 CR#58 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-254139 | Update to TS 33.116 MME SCAS according to NESASG feedback |
draftCR revised to S3-254630 |
ZTE Corporation | SCAS_5GA | Rel-19 |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-254140 | Update to UPF SCAS living doc according to NESASG feedback | draftCR | ZTE Corporation | SCAS_5GA | Rel-19 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254141 | Network product class description for SCAS_NR_Femto |
draftCR revised to S3-254689 |
ZTE Corporation | SCAS_NR_Femto | Rel-20 |
S3-125 AI: 5.1.5 |
revised | [WTS] [JSN] | |
| S3-254142 | Critical assests for SCAS_NR_Femto |
draftCR revised to S3-254690 |
ZTE Corporation | SCAS_NR_Femto | Rel-20 |
S3-125 AI: 5.1.5 |
revised | [WTS] [JSN] | |
| S3-254143 | Network product class description for SCAS_Femto_SeGW |
draftCR revised to S3-254636 |
ZTE Corporation | SCAS_Femto_SeGW | Rel-20 |
S3-125 AI: 5.1.6 |
revised | [WTS] [JSN] | |
| S3-254144 | Test case related to topology hiding for SCAS_Femto_SeGW |
pCR revised to S3-254637 |
ZTE Corporation | 33.547 0.1.0 | SCAS_Femto_SeGW | Rel-20 |
S3-125 AI: 5.1.6 |
revised | [WTS] [JSN] |
| S3-254145 | Threat related to topology hiding for SCAS_Femto_SeGW |
draftCR revised to S3-254638 |
ZTE Corporation | SCAS_Femto_SeGW | Rel-20 |
S3-125 AI: 5.1.6 |
revised | [WTS] [JSN] | |
| S3-254146 | Update the Scope | pCR | ZTE Corporation | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
merged | [WTS] [JSN] |
| S3-254147 | Add evaluation for solution #1.1 |
pCR revised to S3-254751 |
ZTE Corporation | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-254148 | Add evaluation for solution #2.1 |
pCR revised to S3-254612 |
ZTE Corporation | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-254149 | Conclusion for KI#1 | pCR | ZTE Corporation | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
merged | [WTS] [JSN] |
| S3-254150 | Resolve EN in Solution #1.1 |
pCR revised to S3-254604 |
ZTE Corporation | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-254151 | Resolve EN in Solution #2.1 | pCR | ZTE Corporation | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254152 | Add evaluation for solution #1 |
pCR revised to S3-254753 |
ZTE Corporation | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-254153 | Add evaluation for solution #2 |
pCR revised to S3-254588 |
ZTE Corporation | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-254154 | Resolve EN in Solution #1 |
pCR revised to S3-254752 |
ZTE Corporation | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-254155 | Resolve EN in Solution #2 |
pCR revised to S3-254587 |
ZTE Corporation | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-254156 | Solution on group authorization |
pCR revised to S3-254595 |
ZTE Corporation | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-254157 | New key issue on MAC CE security | pCR | ZTE Corporation | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-254158 | Updating introduction of security area#2 to include lower layer secuirty | pCR | ZTE Corporation | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254159 | Solution to KI#1 |
pCR revised to S3-254663 |
ZTE Corporation | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-254160 | Solution on Authentication for AIoT devices | pCR | ZTE Corporation | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
not treated | [WTS] [JSN] |
| S3-254161 | New solution to KI#4 |
pCR revised to S3-254688 |
ZTE Corporation | 33.746 0.2.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.13 |
revised | [WTS] [JSN] |
| S3-254162 | A new annex on security requirement analysis for 6G | pCR | CableLabs | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254163 | New sol on KI#1 |
pCR revised to S3-254722 |
China Telecom Corporation Ltd. | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-254164 | Reply LS on User consent for Data collection at the UE for NW-side model training |
LS out LS is reply to S3-254024 source LS: R2-2506541 LS To: RAN2 |
Nokia | Rel-19 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-254165 | KI on gNB based data collection | draftCR | Nokia | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
noted | [WTS] [JSN] | |
| S3-254166 | Reply LS on UE parameters update header security |
LS out LS is reply to S3-254025 source LS: C1-253719 LS To: CT1, CT4 revised to S3-254550 |
Nokia | TEI19 | Rel-19 |
S3-125 AI: 3 |
revised | [WTS] [JSN] | |
| S3-254167 | Adding a NOTE for clarification regarding security related events |
pCR revised to S3-254683 |
Nokia | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-254168 | Updates for Key Issue#3 | pCR | Nokia | 33.724 0.1.0 | FS_5G_WAB_SEC | Rel-20 |
S3-125 AI: 5.2.14 |
approved | [WTS] [JSN] |
| S3-254169 | Title update for Key Issue #2 | pCR | Nokia | 33.724 0.1.0 | FS_5G_WAB_SEC | Rel-20 |
S3-125 AI: 5.2.14 |
noted | [WTS] [JSN] |
| S3-254170 | Evaluation to solution #3 | pCR | China Telecom Corporation Ltd. | 33.746 0.2.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.13 |
approved | [WTS] [JSN] |
| S3-254171 | Updates to Key Issue#5 |
pCR revised to S3-254684 |
Nokia | 33.746 0.2.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.13 |
revised | [WTS] [JSN] |
| S3-254172 | Update the solution #1 |
pCR revised to S3-254687 |
China Telecom Corporation Ltd. | 33.746 0.2.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.13 |
revised | [WTS] [JSN] |
| S3-254173 | New key issue for support of dynamic CAG for MWAB nodes | pCR | Nokia | 33.724 0.1.0 | FS_5G_WAB_SEC | Rel-20 |
S3-125 AI: 5.2.14 |
noted | [WTS] [JSN] |
| S3-254174 | Evaluation to solution#5 | pCR | China Telecom Corporation Ltd. | 33.746 0.2.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.13 |
approved | [WTS] [JSN] |
| S3-254175 | Revised SID for CAPIF-4 |
SID revised revised to S3-254562 |
Huawei, HiSilicon | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 6.3 |
revised | [WTS] [JSN] | |
| S3-254176 | Scope alignment | pCR | Huawei, HiSilicon | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-254177 | 3GPP consideration for IKEv2 |
pCR revised to S3-254568 |
Huawei, HiSilicon | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-254178 | 3GPP consideration for PKI | pCR | Huawei, HiSilicon | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
merged | [WTS] [JSN] |
| S3-254179 | Updating TLS1.2 and TLS1.3 to include EAP-TTLS and OAuth protocols |
pCR revised to S3-254731 |
Huawei, HiSilicon | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-254180 | Updating PKI to include OCSP protocol |
pCR revised to S3-254732 |
Huawei, HiSilicon | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-254181 | Updating clause 6 for JOSE | pCR | Huawei, HiSilicon | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-254182 | Overall evaluation for solutions | pCR | Huawei, HiSilicon | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254183 | Minutes for Conference Call on Oct 30 | discussion | Huawei, HiSilicon | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
noted | [WTS] [JSN] | |
| S3-254184 | Reply LS on User consent for Data collection at the UE for NW-side model training |
LS out LS is reply to S3-254024 LS To: RAN2 |
vivo | Rel-19 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-254185 | Reply LS on Early Alignment on Access Stratum security aspects |
LS out LS is reply to R2- 2507945 LS To: RAN2 |
vivo | Rel-20 |
S3-125 AI: 3 |
merged | [WTS] [JSN] | ||
| S3-254186 | AIoT correction to the authentication procedures |
CR revision of S3-253677 revised to S3-254724 |
[OPPO, CATT, InterDigital], vivo, [Huawei, HiSilicon, Lenovo, Ericsson, Qualcomm] | 33.369 19.0.0 CR#172 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-254187 | Information protection during command procedure - corrections |
CR revision of S3-253684 revised to S3-254554 |
[Philips International B.V.], vivo | 33.369 19.0.0 CR#562 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-254188 | Correction on privacy |
CR revision of S3-253685 revised to S3-254459, S3-254555 |
vivo, [Lenovo, ZTE, OPPO, Qualcomm, Huawei, InterDigital, CATT] | 33.369 19.0.0 CR#202 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-254189 | Add new terms and abbreviations | CR | vivo | 33.369 19.0.0 CR#59 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-254190 | New clause for security related services |
CR revision of S3-253801 |
[Huawei, HiSilicon, Lenovo], vivo | 33.369 19.0.0 CR#352 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-254191 | Correction on privacy | CR | vivo | 33.369 19.0.0 CR#60 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
withdrawn | [WTS] [JSN] |
| S3-254192 | Add abbreviations for LTM | CR | vivo | 33.501 19.4.0 CR#2200 catF | NR_Mob_Ph4_Sec | Rel-19 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254193 | Symmetric solution on SUCI protection |
pCR revised to S3-254736 |
vivo | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-254194 | Revised SID on Core Network Enhanced Support for Artificial Intelligence (AI) Machine Learning (ML) Phase 2 | SID revised | vivo, China Mobile | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 6.3 |
noted | [WTS] [JSN] | |
| S3-254195 | Update on Key Issue #1 |
pCR revised to S3-254586 |
vivo | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
revised | [WTS] [JSN] |
| S3-254196 | Solution Update for Solution#1.2 | pCR | vivo | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254197 | Conclusion for KI#1 | pCR | vivo | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
merged | [WTS] [JSN] |
| S3-254198 | New solution: communication protection |
pCR revised to S3-254695 |
vivo | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-254199 | New solution: privacy protection |
pCR revised to S3-254699 |
vivo | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-254200 | Discussion Paper on Security Area for Data Framework | discussion | vivo, InterDigital, OPPO, China Mobile | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] | |
| S3-254201 | New Security Area: Security and Privacy of Data Framework | pCR | vivo, InterDigital, OPPO, China Mobile, Apple, CATT | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254202 | New key issue of SA#3: Primary Authentication | pCR | vivo | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254203 | New key issue of SA#3: Vulnerability Resolution | pCR | vivo | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254204 | New key issue of SA#3: Subscriber ID Protection | pCR | vivo | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254205 | New key issue of SA#2: SI/Paging Protection | pCR | vivo | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254206 | Update on Annex B: Mapping of Solutions to Key Issues |
pCR revised to S3-254646 |
vivo, Qualcomm | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-254207 | New Solution on AEAD Algorithm Selection |
pCR revised to S3-254664 |
vivo | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-254208 | Update on Key Issue #1 Algorithm Selection | pCR | vivo | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-254209 | Update on Key Issue #2 AEAD algorithm interface | pCR | vivo | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
merged | [WTS] [JSN] |
| S3-254210 | New Key Issue on AEAD Keys |
pCR revised to S3-254658 |
vivo, THALES | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-254211 | New Key Issue and Conclusion on Operational Sequence of AEAD | pCR | vivo | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-254212 | Draft TR 33.700-23 v020 | draft TR | China Telecom Corporation Ltd. | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
approved | [WTS] [JSN] | |
| S3-254213 | pCR for 33.117 on Authorization token verification failure handling in different PLMNs | other | BSI (DE) | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
noted | [WTS] [JSN] | |
| S3-254214 | pCR for 33.117 on unnecessary or insecure services / protocols |
other revised to S3-254621 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-254215 | pCR for 33.117 on Restricted reachability of services |
other revised to S3-254622 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-254216 | pCR for 33.514 on SUPI de-concealment protection schemes |
other revised to S3-254626 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-254217 | pCR for 33.514 on UP security policy configuration for 5G LAN service |
other revised to S3-254625 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-254218 | pCR for 33.521 Clarification of Data Masking |
other revised to S3-254645 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-254219 | draftCR for 33.226 for correction of test case IDs |
draftCR revised to S3-254631 |
BSI (DE), Montsecure | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-254220 | Clean-up of 33.523 |
draftCR revised to S3-254632 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-254221 | pCR for 33.730 conclusion |
other revised to S3-254635 |
BSI (DE) | FS_SCAS_CP | Rel-20 |
S3-125 AI: 5.2.8 |
revised | [WTS] [JSN] | |
| S3-254222 | Update to scope | pCR | Ericsson | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
merged | [WTS] [JSN] |
| S3-254223 | DP on Security Area for PHY Layer Sensing Signals in 6G | discussion | OPPO, BUPT | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] | |
| S3-254224 | Reply LS to RAN2 on Early Alignment on Access Stratum security aspects(R2-2507933) |
LS out LS is reply to S3-254013 LS To: RAN2 |
Apple | Rel-20 |
S3-125 AI: 3 |
merged | [WTS] [JSN] | ||
| S3-254225 | Reply LS to RAN2 on Integrity check failure(R2-2507915) |
LS out LS is reply to S3-254009 LS To: RAN2, CT1 |
Apple | Rel-19 |
S3-125 AI: 3 |
merged | [WTS] [JSN] | ||
| S3-254226 | Reply LS to RAN2 on parameters in paging message (R2-2507920) |
LS out LS is reply to S3-254010 LS To: RAN2 |
Apple | Rel-19 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-254227 | TR33703 - PQC - revision of Solution#1 | pCR | Apple | 33.703 0.1.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254228 | TR33801-01- Upadte the security area#3 | pCR | Apple | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-254229 | TR33801-01- New KI on authentication request replay protection in Authentication Security areas | pCR | Apple | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254230 | TR33801-01- New KI on MAC layer security in RAN security | pCR | Apple | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-254231 | TR33801-01- New KI on long term key leakage in Authentication Security areas | pCR | Apple | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254232 | Reply LS to RAN2 on user consent for AI/ML network data collection(R2-2506541) |
LS out LS is reply to S3-254024 LS To: RAN2, RAN3 |
Apple | Rel-19 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-254233 | DP on user consent for AI/ML network data collection | discussion | Apple |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-254234 | 6G RAN Security Area KI for PHY Signal Security | pCR | OPPO | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254235 | 6G Security- PHY Sensing Signal Attack Model | pCR | OPPO | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254236 | 6G Sensing Security Area Including Lower Layer Security | pCR | OPPO | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254237 | Presentation of Report to TSG: TR 33.730 Study on Security Assurance Specification (SCAS) for Container-based Product | TS or TR cover | Ericsson | FS_SCAS_CP | Rel-20 |
S3-125 AI: 5.2.8 |
approved | [WTS] [JSN] | |
| S3-254238 | Update KI #2 in TR 33.777 | pCR | OPPO | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
merged | [WTS] [JSN] |
| S3-254239 | Removal of Editors Notes |
CR revised to S3-254741 |
Lenovo | 33.501 19.4.0 CR#2201 catF | XRM_Ph2-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-254240 | New solution to detect compromised MWAB nodes using location tracking | pCR | Nokia | 33.724 0.1.0 | FS_5G_WAB_SEC | Rel-20 |
S3-125 AI: 5.2.14 |
noted | [WTS] [JSN] |
| S3-254241 | Terminology Correction |
CR revised to S3-254730 |
Lenovo | 33.501 19.4.0 CR#2202 catF | XRM_Ph2-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-254242 | New solution on authorization of intermediate UE for 5G Ambient IoT | pCR | OPPO | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
not treated | [WTS] [JSN] |
| S3-254243 | Reply LS on Early Alignment on Access Stratum security aspects (R2-2507933) |
LS out LS is reply to S3-254013 source LS: R2-2507933 LS To: RAN 2 revised to S3-254552 |
Lenovo |
S3-125 AI: 3 |
revised | [WTS] [JSN] | |||
| S3-254244 | New KI on MAC-CE security | pCR | Lenovo | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-254245 | New solution to SUCI calculation with symmetric key |
pCR revised to S3-254749 |
Lenovo | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-254246 | New Solution to KI#1 | pCR | Lenovo | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
noted | [WTS] [JSN] |
| S3-254247 | Update of solution 7 |
pCR revised to S3-254605 |
Ericsson | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-254248 | Update of Solution #1.6 |
pCR revised to S3-254606 |
Lenovo | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-254249 | Clarification on the Sensing Profile | pCR | Lenovo | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254250 | Evaluation of Solution #1.6 |
pCR revised to S3-254607 |
Lenovo | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-254251 | Updating sol #3 for SUCI calculation to resolve EN | pCR | HUAWEI TECHNOLOGIES Co. Ltd. | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254252 | Update to Overview of Security related Events Handling | pCR | Huawei, HiSilicon | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
noted | [WTS] [JSN] |
| S3-254253 | Clarification on key update of UE-Satellite-UE in IMS | CR | Huawei, HiSilicon | 33.328 19.1.0 CR#87 catF | 5GSAT_Ph3_SEC | Rel-19 |
S3-125 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-254254 | Reply LS to GSMA NESASG on changes |
LS out LS is reply to GSMA NESASG LS To: GSMA NESASG revised to S3-254634 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-254255 | GSMA NESAS change to TS 33.117 |
other revised to S3-254623 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-254256 | Addressing roaming EN in sol#5 and updating evaluation | pCR | Huawei, HiSilicon | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
not treated | [WTS] [JSN] |
| S3-254257 | Addressing key updating EN in sol#5 and updating evaluation | pCR | Huawei, HiSilicon | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
not treated | [WTS] [JSN] |
| S3-254258 | living document to TS 33.513 |
draftCR revised to S3-254628 |
Huawei, HiSilicon, CAICT, China Telecom Corporation Ltd. | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-254259 | living document to TS 33.514 |
draftCR revised to S3-254627 |
Huawei, HiSilicon, CAICT, China Telecom Corporation Ltd. | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-254260 | New WID on Security Enhancements for SEAL Data Delivery-phase 3 | WID new | Huawei, HiSilicon | Rel-20 |
S3-125 AI: 6.1 |
noted | [WTS] [JSN] | ||
| S3-254261 | Discussion paper on Security Enhancements for SEAL Data Delivery Phase 3 | discussion | Huawei, HiSilicon | Rel-20 |
S3-125 AI: 6.1 |
noted | [WTS] [JSN] | ||
| S3-254262 | Add optional Flow ID Parameter for Security of SEALDD Services | CR | Huawei, Hisilicon | 33.434 19.0.0 CR#25 catB | DUMMY | Rel-20 |
S3-125 AI: 6.1 |
not pursued | [WTS] [JSN] |
| S3-254263 | Resolving the ENs on Solution #2 |
pCR revised to S3-254572 |
Huawei, HiSilicon | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
revised | [WTS] [JSN] |
| S3-254264 | Evaluation to Solution #2 | pCR | Huawei, HiSilicon | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
merged | [WTS] [JSN] |
| S3-254265 | Addressing the EN on the security assumption | pCR | Huawei, HiSilicon | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
merged | [WTS] [JSN] |
| S3-254266 | Adding security requirements for the new EMM TRANSPORT message | CR | Huawei, HiSilicon | 33.401 19.1.0 CR#734 catF | TEI19 | Rel-19 |
S3-125 AI: 4.2.1 |
merged | [WTS] [JSN] |
| S3-254267 | reply LS on integrity failure |
LS out LS is reply to S3-254009 source LS: R2-2507915 LS To: RAN2 |
Huawei, HiSilicon | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 3 |
merged | [WTS] [JSN] | |
| S3-254268 | resloving the editor's note on randomness |
CR revised to S3-254553 |
Huawei, HiSilicon | 33.369 19.0.0 CR#61 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-254269 | update to the key issue on authentication | pCR | Huawei, HiSilicon | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
merged | [WTS] [JSN] |
| S3-254270 | solution on information protection for DO-A capable AIOT device |
pCR revised to S3-254696 |
Huawei, HiSilicon | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-254271 | New solution on the details of AEAD interface |
pCR revised to S3-254669 |
Huawei, HiSilicon | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-254272 | New solution on the AEAD algorithm negoiation |
pCR revised to S3-254665 |
Huawei, HiSilicon | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-254273 | Update to the length of security parameters | CR | Huawei, HiSilicon | 33.369 19.0.0 CR#62 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
merged | [WTS] [JSN] |
| S3-254274 | New Solution on Authorization for Exposure of UE Data towards OTT Servers |
pCR revised to S3-254578 |
Huawei, HiSilicon | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
revised | [WTS] [JSN] |
| S3-254275 | New solution about creation of EXTRA_IV |
pCR revised to S3-254670 |
Huawei, HiSilicon | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-254276 | Update solution#4 for key derivation of roaming scenarios | pCR | Huawei, HiSilicon | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
approved | [WTS] [JSN] |
| S3-254277 | EN addressing for solution#4 | pCR | Huawei, HiSilicon | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
not treated | [WTS] [JSN] |
| S3-254278 | EN addressing and evaluation for solution#4 | pCR | Huawei, HiSilicon | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254279 | Add evaluation in Sol#6 of TR 33.700-30 |
pCR revised to S3-254756 |
Huawei, HiSilicon, Samsung | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-254280 | Evaluation to Sol#5 of TR 33.700-30 | pCR | Huawei, HiSilicon | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
merged | [WTS] [JSN] |
| S3-254281 | Evaluation to Sol#7 of TR 33.700-30 | pCR | Huawei, HiSilicon | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
not treated | [WTS] [JSN] |
| S3-254282 | New Solution for KI#1 Secure NAS messages via one pair of COUNTs | pCR | Huawei, HiSilicon | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
not treated | [WTS] [JSN] |
| S3-254283 | Address ENs in Sol#6 of TR 33.700-30 |
pCR revised to S3-254755 |
Huawei, HiSilicon, Samsung | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-254284 | BSP4SBA Clause 2.3 Access Token Privilege Restriction (RFC 9700) | pCR | Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
merged | [WTS] [JSN] |
| S3-254285 | BSP4SBA Clause 2.2 Token replay prevention (RFC 9700) |
pCR revised to S3-254711 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-254286 | BSP4SBA Clause 2.5 Client Authentication (RFC 9700) |
pCR revised to S3-254712 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-254287 | BSP4SBA Clause 3.2 Use Appropriate Algorithms (RFC 8725) |
pCR revised to S3-254714 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-254288 | Solution to KI#2 |
pCR revised to S3-254577 |
Huawei, HiSilicon | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
revised | [WTS] [JSN] |
| S3-254289 | BSP4SBA Clause 3.10 Do Not Trust Received Claims (RFC 8725) |
pCR revised to S3-254715 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-254290 | Conclusion to the Best practices | pCR | Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
noted | [WTS] [JSN] |
| S3-254291 | Overall pCR for not applicable Best practice RFC 8725 |
pCR revised to S3-254719 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-254292 | BSP4SBA Clause 3.11 Use Explicit Typing (RFC 8725) |
pCR revised to S3-254716 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-254293 | BSP4SBA Clause 3.8 Validate Issuer and Subject (RFC 8725) |
pCR revised to S3-254717 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-254294 | BSP4SBA Clause 3.9 Use and Validate Audience (RFC 8725) |
pCR revised to S3-254718 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-254295 | Sensing scope alignment |
pCR revised to S3-254603 |
Huawei, HiSilicon | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-254296 | Update Key Issue#2 about the SF architecture alignment | pCR | Huawei, HiSilicon | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
merged | [WTS] [JSN] |
| S3-254297 | Update Solution#2.2 |
pCR revised to S3-254613 |
Huawei, HiSilicon | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-254298 | Address EN and add evaluation to Solution#1.4 |
pCR revised to S3-254608 |
Huawei, HiSilicon | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-254299 | Key Issue on privacy aspect of sensing | pCR | Huawei, HiSilicon | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
merged | [WTS] [JSN] |
| S3-254300 | New security area on the security visibility | pCR | Huawei, HiSilicon, China Mobile, ZTE | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254301 | Clarification about security for MC over IOPS | CR | Huawei, HiSilicon, Motorola Solutions, Ericsson | 33.180 19.3.0 CR#236 catB | MCX20-SEC | Rel-20 |
S3-125 AI: 5.1.2 |
agreed | [WTS] [JSN] |
| S3-254302 | Security for MC 3GPP system | CR | Huawei, HiSilicon | 33.180 19.3.0 CR#237 catB | MCX20-SEC | Rel-20 |
S3-125 AI: 5.1.2 |
not pursued | [WTS] [JSN] |
| S3-254303 | New security area on AIML | pCR | Huawei, HiSilicon | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254304 | Adding scope |
pCR revised to S3-254644 |
Huawei, HiSilicon | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
revised | [WTS] [JSN] |
| S3-254305 | Adding conclusion to MPQUIC | pCR | Huawei, HiSilicon, CableLabs | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
merged | [WTS] [JSN] |
| S3-254306 | Living document to TR 33.926 |
draftCR revised to S3-254620 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-254307 | Living document to TS 33.117 |
draftCR revised to S3-254624 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-254308 | Living document to TS 33.511 |
draftCR revised to S3-254633 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-254309 | Living document to TS 33.512 | draftCR | Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254310 | withdrawn | draftCR | Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
withdrawn | [WTS] [JSN] | |
| S3-254311 | Living document to TS 33.517 | draftCR | Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254312 | Living document to TS 33.518 |
draftCR revised to S3-254618 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-254313 | Living document to TS 33.519 | draftCR | Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254314 | Living document to TS 33.521 |
draftCR revised to S3-254629 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
revised | [WTS] [JSN] | |
| S3-254315 | Living document to TS 33.216 | draftCR | Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254316 | GSMA change to TS 33.511 | other | Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254317 | Overall pCR for not applicable Best practice RFC 9700 |
pCR revised to S3-254713 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-254318 | New Key Issue on Security Aspects for New NAS Security | pCR | Huawei, HiSilicon | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254319 | New Security Area - Network Security | pCR | Huawei, HiSilicon | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-254320 | New Security Area - Security Architecture |
pCR revised to S3-254652 |
Huawei, HiSilicon | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-254321 | KI#2 update |
pCR revised to S3-254611 |
Ericsson | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-254322 | Adding technical baseline text in TS 33.546 |
pCR revised to S3-254743 |
China Unicom | 33.546 0.1.0 | SCAS_NR_Femto | Rel-20 |
S3-125 AI: 5.1.5 |
revised | [WTS] [JSN] |
| S3-254323 | Discussion Paper on adding a new Work Task to the SID of FS_IMSRE_SEC | discussion | KDDI, Samsung, vivo | FS_IMSRE_SEC | Rel-20 |
S3-125 AI: 6.3 |
noted | [WTS] [JSN] | |
| S3-254324 | Security Assumptions Update |
pCR revised to S3-254569 |
Lenovo, Motorola Mobility | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
revised | [WTS] [JSN] |
| S3-254325 | Updates to Solution#1 |
pCR revised to S3-254573 |
Lenovo, Motorola Mobility | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
revised | [WTS] [JSN] |
| S3-254326 | Solution to KI#2 |
pCR revised to S3-254574 |
Lenovo, Motorola Mobility | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
revised | [WTS] [JSN] |
| S3-254327 | Updates to KI#1 to align with SA6 Progress |
pCR revised to S3-254570 |
Lenovo, Motorola Mobility | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
revised | [WTS] [JSN] |
| S3-254328 | Initial high-level Conclusion |
pCR revised to S3-254727 |
Lenovo, Motorola Mobility | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
revised | [WTS] [JSN] |
| S3-254329 | Correction to HQC |
pCR revised to S3-254565 |
Lenovo, Motorola Mobility | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-254330 | Solution for PQC based SUCI Computation |
pCR revised to S3-254728 |
Lenovo, Motorola Mobility | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-254331 | Solution for Hybrid PQC based SUCI Computation | pCR | Lenovo, Motorola Mobility | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
noted | [WTS] [JSN] |
| S3-254332 | Abnormal behaviour identification over UE-N/W connection to improve security |
pCR revision of S3-253674 |
Lenovo, Motorola Mobility, T-Mobile US, Deutsche Telekom, AT&T, SK Telecom, China Mobile, Telefonica, Interdigital, CATT, China Telecom, ZTE, Telecom Italia | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-254333 | Discussions on Abnormal behaviour identification over UE-N/W connection to improve security | discussion | Lenovo, Motorola Mobility, SK Telecom | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] | |
| S3-254334 | LS reply on CVD-2024-0096 – SNI5GECT: A Practical Approach to Inject aNRchy into 5G NR |
LS out LS is reply to S3-253105 LS To: GSMA FASG CVD, 3GPP RAN2 revision of S3-253651 |
Nokia |
S3-125 AI: 7 |
noted | [WTS] [JSN] | |||
| S3-254335 | Scope of TR 33.714 |
pCR revised to S3-254694 |
THALES | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-254336 | KI#2 |
pCR revised to S3-254705 |
THALES | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-254337 | KI#2: solution for DO-A capable AIoT devices | pCR | THALES | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
not treated | [WTS] [JSN] |
| S3-254338 | Evaluation of solution #1 | pCR | THALES, ORANGE | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254339 | Evaluation of solution #2 | pCR | THALES, ORANGE | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254340 | Evaluation of solution #3 | pCR | THALES, ORANGE | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254341 | Evaluation of solution #4 | pCR | THALES, ORANGE | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254342 | EN resolution for solution #5 | pCR | LG Electronics | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254343 | EN resolution for solution #6 | pCR | LG Electronics | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254344 | New key issue for MAC layer protection | pCR | LG Electronics | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-254345 | Evaluation of solution #5 | pCR | THALES, ORANGE | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254346 | Evaluation of solution #6 | pCR | THALES, ORANGE | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254347 | Solution #8 | pCR | THALES, ORANGE | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254348 | Evaluation of solution #9 |
pCR revised to S3-254737 |
THALES, ORANGE | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-254349 | Evaluation of solution #10 |
pCR revised to S3-254738 |
THALES, ORANGE | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
revised | [WTS] [JSN] |
| S3-254350 | Evaluation of solution #11 | pCR | THALES, ORANGE | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254351 | Update to SA3-LI ToR |
ToR revised to S3-254708 |
SA3-LI Chair |
S3-125 AI: 2.2 |
revised | [WTS] [JSN] | |||
| S3-254352 | New Key issue on MAC CE security | pCR | OPPO | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-254353 | CR to TS33.369 Update privacy general clause for privacy policy pre-configuration |
CR revision of S3-253676 |
Lenovo [CATT] | 33.369 19.0.0 CR#252 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-254354 | DP on MAC CE Security Threats in 6G | discussion | OPPO | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] | ||
| S3-254355 | Add New Annex Hiding Process | pCR | vivo Mobile Communication Co., | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
not treated | [WTS] [JSN] |
| S3-254356 | Information protection during command procedure - corrections |
CR revision of S3-253684 |
Lenovo [Philips International B.V.] | 33.369 19.0.0 CR#563 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
withdrawn | [WTS] [JSN] |
| S3-254357 | Addressing the missing information on the initial value of temporary identifier in Clause 5.4.3 and Annex B. |
CR revision of S3-253854 revised to S3-254725 |
Lenovo [Ericsson] | 33.369 19.0.0 CR#552 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-254358 | Pseudo-CR-Add test case for location verification in TS 33.546 | pCR | China Mobile Com. Corporation | 33.546 0.1.0 | SCAS_NR_Femto | Rel-20 |
S3-125 AI: 5.1.5 |
noted | [WTS] [JSN] |
| S3-254359 | Pseudo-CR-Add test case for Hosting party authentication of TS 33.546 |
pCR revised to S3-254693 |
China Mobile Com. Corporation | 33.546 0.1.0 | SCAS_NR_Femto | Rel-20 |
S3-125 AI: 5.1.5 |
revised | [WTS] [JSN] |
| S3-254360 | Clarification for requirements on privacy | CR | Ericsson | 33.369 19.0.0 CR#63 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-254361 | Removing the Editor's Note related to requirements of identifier privacy | CR | Ericsson | 33.369 19.0.0 CR#64 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254362 | Updating potential security requirements in key issue on resource exhaustion | pCR | Ericsson | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
not treated | [WTS] [JSN] |
| S3-254363 | New Solution for group paging in a privacy preserving manner |
pCR revised to S3-254701 |
Ericsson | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-254364 | New Solution for privacy-presserving responses from individual devices to group paging |
pCR revised to S3-254700 |
Ericsson | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-254365 | Security area#3: Clarification regarding access agnostic authentication | pCR | Ericsson, Orange | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-254366 | Reducing the impact of long-term shared secret key leakage | pCR | Ericsson | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254367 | Reply LS on integrity failure |
LS out LS is reply to S3-254009 source LS: R2-2507915 LS To: RAN2 revised to S3-254547 |
Beijing Xiaomi Mobile Software | Rel-19 |
S3-125 AI: 3 |
revised | [WTS] [JSN] | ||
| S3-254368 | Update Key issue #1 for 5G Ambient IoT services | pCR | Beijing Xiaomi Mobile Software | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
merged | [WTS] [JSN] |
| S3-254369 | Update Key issue #2 for 5G Ambient IoT services | pCR | Beijing Xiaomi Mobile Software | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
merged | [WTS] [JSN] |
| S3-254370 | New solution of authentication and security establishment for DO-A capable device | pCR | Beijing Xiaomi Mobile Software | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
not treated | [WTS] [JSN] |
| S3-254371 | Address the ENs in solution #5 |
pCR revised to S3-254754 |
Beijing Xiaomi Mobile Software | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-254372 | Add the evaluation of solution #5 |
pCR revised to S3-254591 |
Beijing Xiaomi Mobile Software | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-254373 | New solution for AEAD algorithms negotiation |
pCR revised to S3-254666 |
Beijing Xiaomi Mobile Software | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-254374 | New Key Issue of re-authentication in roaming scenarios in security area #3 | pCR | Beijing Xiaomi Mobile Software | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254375 | New Key Issue of subscriber identifier privacy in security area #3 | pCR | Beijing Xiaomi Mobile Software | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254376 | New Security Area on security and privacy aspects of network exposure | pCR | Xiaomi Communications | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-254377 | Update TR 33.785 sol#5 |
pCR revised to S3-254583 |
Xiaomi Communications | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
revised | [WTS] [JSN] |
| S3-254378 | New sol for TR 33.785 KI#2 |
pCR revised to S3-254579 |
Xiaomi Communications | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
revised | [WTS] [JSN] |
| S3-254379 | New sol for TR 33.700-23 KI#1 |
pCR revised to S3-254596 |
Xiaomi Communications | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-254380 | New sol for TR 33.700-23 KI#2 |
pCR revised to S3-254599 |
Xiaomi Communications | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-254381 | New sol for TR 33.700-23 KI#3 |
pCR revised to S3-254601 |
Xiaomi Communications | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-254382 | New KI on ISAC privacy | pCR | Xiaomi Communications | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
merged | [WTS] [JSN] |
| S3-254383 | Intermediate conclusion for KI#1 |
pCR revised to S3-254610 |
Xiaomi Communications | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-254384 | Reply LS on user consent for data collection at the UE for NW-side model training |
LS out LS is reply to S3-254024 source LS: R2-2506541 LS To: RAN2, RAN3, SA5 |
Xiaomi EV Technology | Rel-19 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-254385 | Reply LS on Early Alignment on Access Stratum security aspects |
LS out LS is reply to S3-254013 source LS: R2-2507945 LS To: RAN2 |
Xiaomi EV Technology | Rel-20 |
S3-125 AI: 3 |
merged | [WTS] [JSN] | ||
| S3-254386 | Update to Solution #2 | pCR | Xiaomi EV Technology | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
not treated | [WTS] [JSN] |
| S3-254387 | Resolution of Editor’s Note for Key Update in Solution #3 | pCR | Xiaomi EV Technology | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
not treated | [WTS] [JSN] |
| S3-254388 | Resolution of Editor’s Note for Home-routed Roaming in Solution #3 |
pCR revised to S3-254640 |
Xiaomi EV Technology | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
revised | [WTS] [JSN] |
| S3-254389 | Conclusion on PSK support for MPQUIC TLS | pCR | Xiaomi EV Technology | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
merged | [WTS] [JSN] |
| S3-254390 | New Security Area on Sensing Security and Privacy | pCR | Xiaomi EV Technology, InterDigital | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254391 | New Key Issue for SA#1 on Security for 6G NAS | pCR | Xiaomi EV Technology | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254392 | New Key Issue for SA2#2 on Security Enhancement for RAN User Plane | pCR | Xiaomi EV Technology | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254393 | New Key Issue for SA#2 on Security Enhancement for RAN Mobility | pCR | Xiaomi EV Technology | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254394 | Pseudo-CR-Add test case for device authentication in TS 33.546 |
pCR revised to S3-254692 |
China Mobile Com. Corporation | 33.546 0.1.0 | SCAS_NR_Femto | Rel-20 |
S3-125 AI: 5.1.5 |
revised | [WTS] [JSN] |
| S3-254395 | Update Annex with NR Femto authentication threat in TS 33.926 | draftCR | China mobile | SCAS_NR_Femto | Rel-19 |
S3-125 AI: 5.1.5 |
withdrawn | [WTS] [JSN] | |
| S3-254396 | Way forward for the IMS Data Channel and LI cases | discussion | Ericsson | Rel-18 |
S3-125 AI: 4.1.1 |
noted | [WTS] [JSN] | ||
| S3-254397 | Rel-18 Corrections for IMS Data Channels and LI | CR | Ericsson | 33.328 18.4.0 CR#88 catF | NG_RTC_SEC_Ph2 | Rel-18 |
S3-125 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-254398 | Rel-19 Corrections for IMS Data Channels and LI |
CR revised to S3-254721 |
Ericsson | 33.328 19.1.0 CR#89 catA | NG_RTC_SEC_Ph2 | Rel-19 |
S3-125 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-254399 | Alignment of AKMA UE ID exposure via NEF with TS 23.502 | CR | Ericsson | 33.535 19.0.0 CR#235 catF | TEI19 | Rel-19 |
S3-125 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-254400 | Pseudo-CR on Event source | pCR | Ericsson | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
merged | [WTS] [JSN] |
| S3-254401 | Pseudo-CR on Event identifiers | pCR | Ericsson | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
merged | [WTS] [JSN] |
| S3-254402 | Pseudo-CR on NF Consumer (malformed message) | pCR | Ericsson | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
merged | [WTS] [JSN] |
| S3-254403 | Pseudo-CR on Message type | pCR | Ericsson | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
merged | [WTS] [JSN] |
| S3-254404 | Pseudo-CR on NF Consumer (authorization failure) | pCR | Ericsson | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
merged | [WTS] [JSN] |
| S3-254405 | Pseudo-CR on Security events related to authentication failure |
pCR revised to S3-254676 |
Ericsson | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-254406 | Pseudo-CR on Prevention of DoS attacks on the Security related events collection entity |
pCR revised to S3-254674 |
Ericsson | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-254407 | Pseudo-CR on Data related to massive number of messages | pCR | Ericsson | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
merged | [WTS] [JSN] |
| S3-254408 | Pseudo-CR on adapting best practice for protecting redirect-based flows | pCR | Ericsson | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
merged | [WTS] [JSN] |
| S3-254409 | Pseudo-CR on adapting best practice for resource owner password credentials grant | pCR | Ericsson | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
merged | [WTS] [JSN] |
| S3-254410 | Pseudo-CR on BCP for access token privilege restriction |
pCR revised to S3-254710 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
revised | [WTS] [JSN] |
| S3-254411 | Pseudo-CR on Security Area: UE to Core Network security, security anchor |
pCR revised to S3-254649 |
Ericsson | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-254412 | New Security Area on Data collection for security monitoring |
pCR revised to S3-254656 |
Ericsson, AT&T, Lenovo, MITRE, Motorola Mobility, NSA, TMO US | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-254413 | Pseudo-CR on System overview for the Attacker model |
pCR revised to S3-254647 |
Ericsson | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-254414 | New SID on the security support for the Next Generation Real Time Communication services Phase 3 | SID new | Ericsson | Rel-20 |
S3-125 AI: 6.1 |
noted | [WTS] [JSN] | ||
| S3-254415 | New WID on the security support for the Next Generation Real Time Communication services Phase 3 | WID new | Ericsson | Rel-20 |
S3-125 AI: 6.1 |
noted | [WTS] [JSN] | ||
| S3-254416 | Pseudo-CR on 6.3.3 of TR 33.703 | pCR | China Mobile | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
merged | [WTS] [JSN] |
| S3-254417 | Overview and Assumption for AEAD |
pCR revised to S3-254657 |
vivo Mobile Communication Co., | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
revised | [WTS] [JSN] |
| S3-254418 | Clarification of key lengths and length of RE/XRES |
CR revised to S3-254556 |
Lenovo | 33.369 19.0.0 CR#65 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-254419 | Reply LS on integrity failure |
LS out LS is reply to S3-254009 LS To: RAN2 |
Nokia | AmbientIoT-SEC | Rel-20 |
S3-125 AI: 3 |
merged | [WTS] [JSN] | |
| S3-254420 | Reply LS on Security parameter in A-IoT paging |
LS out LS is reply to S3-254010 LS To: RAN2 revised to S3-254720 |
Nokia | AmbientIoT-SEC | Rel-20 |
S3-125 AI: 3 |
revised | [WTS] [JSN] | |
| S3-254421 | KI2: Security threats and requirements | pCR | Nokia | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
merged | [WTS] [JSN] |
| S3-254422 | KI1: security threats and requirements |
pCR revised to S3-254706 |
Nokia | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-254423 | New key issue on 6G authentication enhancements | pCR | Nokia | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254424 | New key issue on 6G re-authentication optimization | pCR | Nokia | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254425 | Update Annex with NR Femto location threats in TR 33.926 | other | China Mobile Com. Corporation | SCAS_NR_Femto | Rel-20 |
S3-125 AI: 5.1.5 |
noted | [WTS] [JSN] | |
| S3-254426 | Add an Annex for NR Femto in TR 33.926 | other | China Mobile Com. Corporation | Rel-20 |
S3-125 AI: 5.1.5 |
merged | [WTS] [JSN] | ||
| S3-254427 | Update Annex with NR Femto critical assets in TR 33.926 | other | China mobile |
S3-125 AI: 5.1.5 |
merged | [WTS] [JSN] | |||
| S3-254428 | Granular authorization for OTT/AF |
pCR revised to S3-254580 |
Nokia | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
revised | [WTS] [JSN] |
| S3-254429 | Solution 1 update for key generation |
pCR revised to S3-254584 |
Nokia | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
revised | [WTS] [JSN] |
| S3-254430 | Update Annex with NR Femto authentication threat in TR 33.926 |
other revised to S3-254691 |
China mobile |
S3-125 AI: 5.1.5 |
revised | [WTS] [JSN] | |||
| S3-254431 | Update SeGW description for Annex X.1 in TR 33.926 | other | China mobile |
S3-125 AI: 5.1.6 |
merged | [WTS] [JSN] | |||
| S3-254432 | pCR to TS 33.502 – Addressing ENs in clause 6 |
pCR revised to S3-254682 |
Vodafone | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-254433 | AioT correction to the authentication procedures |
CR revision of S3-253677 |
Ericsson | 33.369 19.0.0 CR#173 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-254434 | DO-A Capable AIoT device identifier protection with Bloom filter |
pCR revised to S3-254702 |
Xidian University, OPPO | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-254435 | Discussion on R20 AIOT security | discussion | OPPO | Rel-20 |
S3-125 AI: 5.2.11 |
not treated | [WTS] [JSN] | ||
| S3-254436 | Evaluation for solution #1 | pCR | Samsung | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254437 | Evaluation for solution #5 | pCR | Samsung | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254438 | Evaluation for solution #6 | pCR | Samsung | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254439 | pCR to merge all Hybrid solutions together | pCR | Samsung | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
noted | [WTS] [JSN] |
| S3-254440 | pCR to update solution #10 | pCR | Samsung | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254441 | Pseudo-CR to resolve EN in configuration of security related events | pCR | Samsung | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
merged | [WTS] [JSN] |
| S3-254442 | [draft] Reply LS on Early Alignment on Access Stratum security aspects |
LS out LS is reply to S3-254013 source LS: R2-2507945 LS To: RAN2 |
Samsung | Rel-20 |
S3-125 AI: 3 |
merged | [WTS] [JSN] | ||
| S3-254443 | Revised SID on Security Aspects for IMS resiliency | SID revised | Samsung, KDDI, vivo | FS_IMSRE_SEC | Rel-20 |
S3-125 AI: 6.3 |
noted | [WTS] [JSN] | |
| S3-254444 | FL member authorization for AIMLE services |
pCR revised to S3-254575 |
Samsung | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
revised | [WTS] [JSN] |
| S3-254445 | Update to Security Area - RAN Security | pCR | Samsung, SK Telecom | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254446 | Key issue for MAC CE protection | pCR | Samsung, SK Telecom | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
merged | [WTS] [JSN] |
| S3-254447 | Key issue for initial RACH protection | pCR | Samsung, SK Telecom | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254448 | Key issue for unprotected system information | pCR | Samsung, SK Telecom | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254449 | Key Issue on security for interworking | pCR | Samsung | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254450 | Key Issue on protection against SUCI replay attack | pCR | Samsung | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254451 | Update to KI#2 on security protection of compromised WAB nodes | pCR | Samsung | 33.724 0.1.0 | FS_5G_WAB_SEC | Rel-20 |
S3-125 AI: 5.2.14 |
noted | [WTS] [JSN] |
| S3-254452 | [draft] Reply LS on User consent for data collection at the UE for NW-side model training |
LS out LS is reply to S3-254024 source LS: R2-2506541 LS To: RAN2 |
Samsung | Rel-19 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-254453 | Update on KI#1 | pCR | Samsung | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
merged | [WTS] [JSN] |
| S3-254454 | Update on KI#2 | pCR | Samsung | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
merged | [WTS] [JSN] |
| S3-254455 | Group authorization for UE-deployed API invoker accessing other UEs' resources of a group |
pCR revised to S3-254723 |
Samsung | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
revised | [WTS] [JSN] |
| S3-254456 | Reply LS on Security parameter in A-IoT paging |
LS out LS is reply to S3-254010 LS To: RAN2 |
China Mobile | Rel-20 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-254457 | Update Solution#3 for removing ENs and adding evaluation |
pCR revised to S3-254589 |
CATT | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
revised | [WTS] [JSN] |
| S3-254458 | New solution on download task management for S&F operations | pCR | CATT | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
not treated | [WTS] [JSN] |
| S3-254459 | Correction on privacy |
CR revision of S3-254188 |
Ericsson | 33.369 19.0.0 CR#203 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
merged | [WTS] [JSN] |
| S3-254460 | Update KI on AIOT authenticaiton | pCR | OPPO | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
merged | [WTS] [JSN] |
| S3-254461 | New solution on NAS keys isolation in S&F operations | pCR | CATT | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
not treated | [WTS] [JSN] |
| S3-254462 | Update KI on AIOT device ID protection in DO-A procedure |
pCR revised to S3-254698 |
OPPO | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-254463 | New WID on Security related Events Handling |
WID revised revision of SP-250876 revised to S3-254757 |
Vodafone | SECHAND | Rel-20 |
S3-125 AI: 6.3 |
revised | [WTS] [JSN] | |
| S3-254464 | Update KI on intermediate UE authorization | pCR | OPPO | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
merged | [WTS] [JSN] |
| S3-254465 | Reply LS on integrity failure |
LS out LS is reply to S3-254009/R2-2507915 LS To: RAN2 |
CATT | Rel-19 |
S3-125 AI: 3 |
merged | [WTS] [JSN] | ||
| S3-254466 | KI on long term credential management | pCR | SK Telecom | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254467 | CR to TS33.369 Update identifier privacy requirements | CR | CATT | 33.369 19.0.0 CR#66 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-254468 | KI on SIB protection | pCR | SK Telecom | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254469 | CR to TS33.369 define the length of (X)RES | CR | CATT | 33.369 19.0.0 CR#67 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
merged | [WTS] [JSN] |
| S3-254470 | Agenda |
agenda revision of S3-254000 |
SA WG3 Chair |
S3-125 AI: 1 |
approved | [WTS] [JSN] | |||
| S3-254471 | Update Key Issue#1 for adding threaten and requirement | pCR | CATT | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
merged | [WTS] [JSN] |
| S3-254472 | Update Key Issue#2 for adding threaten and requirement | pCR | CATT | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
merged | [WTS] [JSN] |
| S3-254473 | Update Solution#3 Security of connection between UE and Data Collection NF |
pCR revised to S3-254585 |
OPPO | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
revised | [WTS] [JSN] |
| S3-254474 | New KI on privacy protection for UE training data collection | pCR | OPPO | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
noted | [WTS] [JSN] |
| S3-254475 | Discussion on privacy protection for UE-side data collection | pCR | OPPO | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
noted | [WTS] [JSN] |
| S3-254476 | Reply LS on User consent for Data collection at the UE for NW-side model training |
LS out LS is reply to S3-254024 LS To: RAN2, RAN3 |
OPPO | Rel-19 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-254477 | Conclusion for MPQUIC study | pCR | Ericsson | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
noted | [WTS] [JSN] |
| S3-254478 | Pseudo-CR on key issue related to MAC layer risk mitigation |
pCR revised to S3-254655 |
Ericsson | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-254479 | Pseudo-CR on Security of UE connection setup with Data Collection NF using TLS |
pCR revised to S3-254581 |
Ericsson | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
revised | [WTS] [JSN] |
| S3-254480 | KI#2: solution for AIoT devices 1 | pCR | THALES | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
not treated | [WTS] [JSN] |
| S3-254481 | Pseudo-CR on Security of UE data exposure towards OTT servers | pCR | Ericsson | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
merged | [WTS] [JSN] |
| S3-254482 | Discussion on User consent for data collection at the UE for NW-side model training | discussion | Ericsson, Verizon, Telecom Italia, Vodafone | NR_AIML_air-Core | Rel-19 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |
| S3-254483 | Reply LS on User consent for Data collection at the UE for NW-side model training |
LS out LS is reply to S3-254024 source LS: R2-2506541 LS To: RAN2, RAN3 |
Ericsson, Verizon, Telecom Italia, Vodafone | NR_AIML_air-Core | Rel-19 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |
| S3-254484 | New Security Area on User Consent | pCR | Nokia, InterDigital | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254485 | 5GC Signaling Traffic Monitoring Security Requirements |
CR revised to S3-254558 |
Ericsson | 33.501 19.4.0 CR#2203 catF | MonStra-Sec | Rel-19 |
S3-125 AI: 4.1.1 |
revised | [WTS] [JSN] |
| S3-254486 | (Draft) Reply LS on Early Alignment on Access Stratum security aspects |
LS out LS is reply to S3-254013 LS To: RAN2 |
OPPO | Rel-20 |
S3-125 AI: 3 |
merged | [WTS] [JSN] | ||
| S3-254487 | New KI on running AEAD without including MAC | pCR | OPPO | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-254488 | TR 33.714 Scope | pCR | OPPO | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
merged | [WTS] [JSN] |
| S3-254489 | new Solution on Protecting Information |
pCR revised to S3-254697 |
OPPO | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-254490 | pCR to TS 33.502 – Detecting SBA layer parameters change |
pCR revised to S3-254679 |
Vodafone | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
revised | [WTS] [JSN] |
| S3-254491 | Reply LS on R2-2507915 on integrity failure |
LS out LS is reply to S3-254009 LS To: RAN2 |
OPPO |
S3-125 AI: 3 |
merged | [WTS] [JSN] | |||
| S3-254492 | Update solution #1.3 in TR 33.777 |
pCR revised to S3-254609 |
OPPO | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
revised | [WTS] [JSN] |
| S3-254493 | Adding a NOTE to the authentication requirements in inventory service | CR | China Mobile | 33.369 19.0.0 CR#68 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
withdrawn | [WTS] [JSN] |
| S3-254494 | Adding NORDAT procedures to TS 33.401 |
CR revision of S3-253524 revised to S3-254549 |
Qualcomm Incorporated, Eutelsat Group, Iridium, Viasat, Sateliot, Novamint, Skylo, Thales, Ericsson, Nokia, Vivo, EchoStar | 33.401 19.1.0 CR#7311 catF | TEI19 | Rel-19 |
S3-125 AI: 3 |
revised | [WTS] [JSN] |
| S3-254495 | Pseudo-CR on Key issue on AEAD compatibility with earlier 3GPP systems | pCR | Qualcomm Incorporated | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-254496 | Pseudo-CR on defining standalone algorithms | pCR | Qualcomm Incorporated | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
noted | [WTS] [JSN] |
| S3-254497 | Alignment CR for UPU Header Security |
CR revision of S3-253662 |
Qualcomm Incorporated, Lenovo, Nokia, Ericsson | 33.501 19.4.0 CR#21832 catF | TEI19 | Rel-19 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254498 | Pseudo-CR on evaluation update for solution #1 in MPQUIC |
pCR revised to S3-254639 |
Qualcomm Incorporated | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
revised | [WTS] [JSN] |
| S3-254499 | Pseudo-CR on evaluation update for solution #2 in MPQUIC | pCR | Qualcomm Incorporated | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
not treated | [WTS] [JSN] |
| S3-254500 | Pseudo-CR on evaluation update for solution #3 in MPQUIC | pCR | Qualcomm Incorporated | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
not treated | [WTS] [JSN] |
| S3-254501 | Pseudo-CR on evaluation update for solution #4 in MPQUIC | pCR | Qualcomm Incorporated | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
not treated | [WTS] [JSN] |
| S3-254502 | Pseudo-CR on evaluation update for solution #5 in MPQUIC | pCR | Qualcomm Incorporated | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
not treated | [WTS] [JSN] |
| S3-254503 | Pseudo-CR on evaluation update for solution #6 in MPQUIC | pCR | Qualcomm Incorporated | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
merged | [WTS] [JSN] |
| S3-254504 | Reply LS on integrity failure of AIoT NAS message |
LS out LS is reply to S3-254009 LS To: RAN2 |
Qualcomm Incorporated | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 3 |
merged | [WTS] [JSN] | |
| S3-254505 | Updates on Key Issue #2 | pCR | Qualcomm Incorporated | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
merged | [WTS] [JSN] |
| S3-254506 | Security for RAN mobility | pCR | Qualcomm Incorporated | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254507 | User-plane security in 6G RAN | pCR | Qualcomm Incorporated | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254508 | Robust AS security setup | pCR | Qualcomm Incorporated | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254509 | Update to Security Area #1 |
pCR revised to S3-254648 |
Qualcomm Incorporated | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-254510 | Update to security area #3 | pCR | Qualcomm Incorporated | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254511 | New SID on enhanced security management service about security policy provisioning in 6G |
SID new revised to S3-254561 |
China Mobile |
S3-125 AI: 6.2 |
revised | [WTS] [JSN] | |||
| S3-254512 | New Security Area on Security for Core Network, Interconnect and Roaming |
pCR revised to S3-254653 |
Nokia, Ericsson, Samsung | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-254513 | Not Applicable Best Practices (RFC 8725) - combined version | pCR | Nokia | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
noted | [WTS] [JSN] |
| S3-254514 | Pseudo-CR on not applicable best practice RFC 9700 | pCR | Nokia | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
noted | [WTS] [JSN] |
| S3-254515 | Adding a NOTE to the authentication requirements in inventory service | CR | China Mobile | 33.369 19.0.0 CR#69 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-254516 | KI #4: solution for DO-A capable AIoT devices |
pCR revised to S3-254703 |
THALES | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
revised | [WTS] [JSN] |
| S3-254517 | Update Security area #2 for adding MAC layer security | pCR | CATT | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254518 | Update Security area #3 for adding secondary authentication |
pCR revised to S3-254651 |
CATT | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-254519 | New KI on NSWO authentication in 6G | pCR | CableLabs, Charter Communications, China Telecom, ZTE | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254520 | Adding general description to 4.2.2 |
pCR revised to S3-254734 |
CATT | 33.547 0.1.0 | SCAS_Femto_SeGW | Rel-20 |
S3-125 AI: 5.1.6 |
revised | [WTS] [JSN] |
| S3-254521 | [draft] Reply LS on user consent for NW-side data collection |
LS out LS To: RAN2, RAN3 |
CATT | Rel-19 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | ||
| S3-254522 | New Security Area on User Consent | pCR | CATT | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254523 | security area on AI | pCR | CATT | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254524 | New Security Area on Data Security and Privacy | pCR | CATT, vivo | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254525 | New KI on security and privacy of user identification for Subscription Authentication and Authorization | pCR | CATT | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254526 | New KI on 6G New NAS security for UE to Core Network Security | pCR | CATT | 33.801-01 0.2.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254527 | Updating access-agnostic authentication in Security area #3 |
pCR revised to S3-254650 |
CableLabs, Charter Communications, China Telecom, ZTE | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
revised | [WTS] [JSN] |
| S3-254528 | Attacker model for MAC CE | pCR | OPPO | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254529 | KI on Authentication for 6GS | pCR | Lenovo, Motorola Mobility | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
not treated | [WTS] [JSN] |
| S3-254530 | Remove ENs in solution #2 in TR 33.700-30 | pCR | OPPO | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
merged | [WTS] [JSN] |
| S3-254531 | LS on DTLS for SCTP Progress Report | LS in | IETF |
S3-125 AI: 3 |
postponed | [WTS] [JSN] | |||
| S3-254532 | Draft TS 33.546 | draft TS | China Unicom | SCAS_NR_Femto | Rel-20 |
S3-125 AI: 5.1.5 |
approved | [WTS] [JSN] | |
| S3-254533 | Draft TS 33.547 | draft TS | CICT | SCAS_Femto_SeGW | Rel-20 |
S3-125 AI: 5.1.6 |
approved | [WTS] [JSN] | |
| S3-254534 | Draft TR 33.703 | draft TR | Huawei | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
approved | [WTS] [JSN] | |
| S3-254535 | Draft TR 33.786 | draft TR | Motorola Mobility | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
approved | [WTS] [JSN] | |
| S3-254536 | Draft TR 33.778 | draft TR | Huawei | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
approved | [WTS] [JSN] | |
| S3-254537 | Draft TR 33.785 | draft TR | Vivo | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
approved | [WTS] [JSN] | |
| S3-254538 | Draft TR 33.777 | draft TR | Xiaomi | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] | |
| S3-254539 | Draft TR 33.730 | draft TR | Ericsson | FS_SCAS_CP | Rel-20 |
S3-125 AI: 5.2.8 |
approved | [WTS] [JSN] | |
| S3-254540 | Draft TR 33.700-30 | draft TR | Qualcomm | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
approved | [WTS] [JSN] | |
| S3-254541 | Draft TR 33.714 | draft TR | OPPO | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
approved | [WTS] [JSN] | |
| S3-254542 | Draft TR 33.755 | draft TR | Huawei | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
approved | [WTS] [JSN] | |
| S3-254543 | Draft TR 33.746 | draft TR | ZTE | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.13 |
approved | [WTS] [JSN] | |
| S3-254544 | Draft TR 33.724 | draft TR | China Telecom | FS_5G_WAB_SEC | Rel-20 |
S3-125 AI: 5.2.14 |
approved | [WTS] [JSN] | |
| S3-254545 | Draft TR 33.801-01 | draft TR | ORANGE | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
approved | [WTS] [JSN] | |
| S3-254546 | Draft TR 33.771 | draft TR | Vivo | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
approved | [WTS] [JSN] | |
| S3-254547 | Reply LS on integrity failure |
LS out LS is reply to S3-254009 source LS: R2-2507915 LS To: RAN2 revision of S3-254367 revised to S3-254709 |
Beijing Xiaomi Mobile Software | Rel-19 |
S3-125 AI: 3 |
revised | [WTS] [JSN] | ||
| S3-254548 | Reply to: LS on User consent for Data collection at the UE for NW-side model training |
LS out LS is reply to S3-254024 LS To: RAN2,RAN3 revised to S3-254740 |
NTT-Docomo |
S3-125 AI: 3 |
revised | [WTS] [JSN] | |||
| S3-254549 | Adding NORDAT procedures to TS 33.401 |
CR revision of S3-254494 |
Qualcomm Incorporated, Eutelsat Group, Iridium, Viasat, Sateliot, Novamint, Skylo, Thales, Ericsson, Nokia, Vivo, EchoStar, Huawei, HiSilicon | 33.401 19.1.0 CR#7312 catF | TEI19 | Rel-19 |
S3-125 AI: 3 |
agreed | [WTS] [JSN] |
| S3-254550 | Reply LS on UE parameters update header security |
LS out LS is reply to S3-254025 source LS: C1-253719 LS To: CT1, CT4 revision of S3-254166 |
Nokia | TEI19 | Rel-19 |
S3-125 AI: 3 |
approved | [WTS] [JSN] | |
| S3-254551 | Reply to: Reply LS on Avatar Security Aspects |
LS out LS is reply to S3-254015 LS To: SA2 |
Ericsson |
S3-125 AI: 3 |
approved | [WTS] [JSN] | |||
| S3-254552 | Reply LS on Early Alignment on Access Stratum security aspects (R2-2507933) |
LS out LS is reply to S3-254013 source LS: R2-2507933 LS To: RAN 2 revision of S3-254243 |
Lenovo |
S3-125 AI: 3 |
approved | [WTS] [JSN] | |||
| S3-254553 | resloving the editor's note on randomness |
CR revision of S3-254268 |
Huawei, HiSilicon | 33.369 19.0.0 CR#611 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-254554 | Information protection during command procedure - corrections |
CR revision of S3-254187 |
Philips International B.V., vivo | 33.369 19.0.0 CR#564 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254555 | Correction on privacy |
CR revision of S3-254188 |
vivo | 33.369 19.0.0 CR#204 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254556 | Clarification of key lengths and length of RE/XRES |
CR revision of S3-254418 |
Lenovo | 33.369 19.0.0 CR#651 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254557 | Add new terms and abbreviations | CR | vivo | 33.369 19.0.0 CR#591 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
withdrawn | [WTS] [JSN] |
| S3-254558 | 5GC Signaling Traffic Monitoring Security Requirements |
CR revision of S3-254485 |
Ericsson | 33.501 19.4.0 CR#22031 catF | MonStra-Sec | Rel-19 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254559 | Open Consultation on the Vertical Standards Relating to the EU Cyber Resilience Act (CRA) | LS in | ETSI TC CYBER |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-254560 | Security Assurance Specification (SCAS) for the CAPIF Core Function |
WID new revision of S3-254028 |
BSI (DE) | Rel-20 |
S3-125 AI: 6.1 |
agreed | [WTS] [JSN] | ||
| S3-254561 | New SID on enhanced security management service about security policy provisioning in 6G |
SID new revision of S3-254511 |
China Mobile |
S3-125 AI: 6.2 |
agreed | [WTS] [JSN] | |||
| S3-254562 | Revised SID for CAPIF-4 |
SID revised revision of S3-254175 |
Huawei, HiSilicon | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 6.3 |
agreed | [WTS] [JSN] | |
| S3-254563 | 6G Security study - working procedures and priorities for the next meeting | discussion | ORANGE |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] | |||
| S3-254564 | Pseudo-CR on NIST security level recommendations |
pCR revision of S3-254052 |
NCSC, NTAC, BT, BSI, US NSA, NPL, DSIT | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-254565 | Correction to HQC |
other revision of S3-254329 |
Lenovo, Motorola Mobility | Rel-20 |
S3-125 AI: 5.2.1 |
approved | [WTS] [JSN] | ||
| S3-254566 | Updating 3GPP Considerations for TLS 1.2 |
pCR revision of S3-254088 |
Ericsson | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-254567 | Updating 3GPP Considerations for TLS 1.3 |
pCR revision of S3-254089 |
Ericsson | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-254568 | 3GPP consideration for IKEv2 |
pCR revision of S3-254177 |
Huawei, HiSilicon | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-254569 | Security Assumptions Update |
pCR revision of S3-254324 |
Lenovo, Motorola Mobility | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
approved | [WTS] [JSN] |
| S3-254570 | Updates to KI#1 to align with SA6 Progress |
pCR revision of S3-254327 |
Lenovo, Motorola Mobility | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
approved | [WTS] [JSN] |
| S3-254571 | Solution on authorization for ML and FL operations |
pCR revision of S3-254106 |
Ericsson | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
approved | [WTS] [JSN] |
| S3-254572 | Resolving the ENs on Solution #2 |
pCR revision of S3-254263 |
Huawei, HiSilicon | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
approved | [WTS] [JSN] |
| S3-254573 | Updates to Solution#1 |
pCR revision of S3-254325 |
Lenovo, Motorola Mobility | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
approved | [WTS] [JSN] |
| S3-254574 | Solution to KI#2 |
pCR revision of S3-254326 |
Lenovo, Motorola Mobility | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
approved | [WTS] [JSN] |
| S3-254575 | FL member authorization for AIMLE services |
pCR revision of S3-254444 |
Samsung | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
approved | [WTS] [JSN] |
| S3-254576 | New Solution Security for UE-side data collection exposure |
pCR revision of S3-254039 |
InterDigital Finland Oy | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
approved | [WTS] [JSN] |
| S3-254577 | Solution to KI#2 |
pCR revision of S3-254288 |
Huawei, HiSilicon | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
approved | [WTS] [JSN] |
| S3-254578 | New Solution on Authorization for Exposure of UE Data towards OTT Servers |
pCR revision of S3-254274 |
Huawei, HiSilicon | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
approved | [WTS] [JSN] |
| S3-254579 | New sol for TR 33.785 KI#2 |
pCR revision of S3-254378 |
Xiaomi Communications | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
approved | [WTS] [JSN] |
| S3-254580 | Granular authorization for OTT/AF |
pCR revision of S3-254428 |
Nokia | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
approved | [WTS] [JSN] |
| S3-254581 | Pseudo-CR on Security of UE connection setup with Data Collection NF using TLS |
pCR revision of S3-254479 |
Ericsson | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
approved | [WTS] [JSN] |
| S3-254582 | Update solution #2 |
pCR revision of S3-254038 |
InterDigital Finland Oy | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
approved | [WTS] [JSN] |
| S3-254583 | Update TR 33.785 sol#5 |
pCR revision of S3-254377 |
Xiaomi Communications | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
approved | [WTS] [JSN] |
| S3-254584 | Solution 1 update for key generation |
pCR revision of S3-254429 |
Nokia | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
approved | [WTS] [JSN] |
| S3-254585 | Update Solution#3 Security of connection between UE and Data Collection NF |
pCR revision of S3-254473 |
OPPO | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
approved | [WTS] [JSN] |
| S3-254586 | Update on Key Issue #1 |
pCR revision of S3-254195 |
vivo | 33.785 0.2.0 | FS_AIML_CN_Ph2_SEC | Rel-20 |
S3-125 AI: 5.2.6 |
approved | [WTS] [JSN] |
| S3-254587 | Resolve EN in Solution #2 |
pCR revision of S3-254155 |
ZTE Corporation | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-254588 | Add evaluation for solution #2 |
pCR revision of S3-254153 |
ZTE Corporation | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-254589 | Update Solution#3 for removing ENs and adding evaluation |
pCR revision of S3-254457 |
CATT | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-254590 | EN removal for Solution #4 to Key Issue #1 |
pCR revision of S3-254117 |
Sateliot, Novamint | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-254591 | Add the evaluation of solution #5 |
pCR revision of S3-254372 |
Beijing Xiaomi Mobile Software | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-254592 | EN Removal for Solution for NAS COUNT synchronization in store-and-forward operations |
pCR revision of S3-254071 |
Nokia | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-254593 | Pseudo-CR on KI#4 of CAPIF |
pCR revision of S3-254081 |
Nokia | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
noted | [WTS] [JSN] |
| S3-254594 | Solution for Group-UE-hosted API invoker authorization |
pCR revision of S3-254102 |
Ericsson | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-254595 | Solution on group authorization |
pCR revision of S3-254156 |
ZTE Corporation | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-254596 | New sol for TR 33.700-23 KI#1 |
pCR revision of S3-254379 |
Xiaomi Communications | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-254597 | Pseudo-CR on Solution for Open Discovery Service |
pCR revision of S3-254080 |
Nokia | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-254598 | Solution for Open Service Discovery |
pCR revision of S3-254101 |
Ericsson | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-254599 | New sol for TR 33.700-23 KI#2 |
pCR revision of S3-254380 |
Xiaomi Communications | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-254600 | New Solution for more granular authorization based on purpose information |
pCR revision of S3-254103 |
Ericsson | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-254601 | New sol for TR 33.700-23 KI#3 |
pCR revision of S3-254381 |
Xiaomi Communications | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-254602 | Pseudo-CR on Solution for purpose of information |
pCR revision of S3-254079 |
Nokia | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-254603 | Sensing scope alignment |
pCR revision of S3-254295 |
Huawei, HiSilicon | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254604 | Resolve EN in Solution #1.1 |
pCR revision of S3-254150 |
ZTE Corporation | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254605 | Update of solution 7 |
pCR revision of S3-254247 |
Ericsson | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254606 | Update of Solution #1.6 |
pCR revision of S3-254248 |
Lenovo | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254607 | Evaluation of Solution #1.6 |
pCR revision of S3-254250 |
Lenovo | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254608 | Address EN and add evaluation to Solution#1.4 |
pCR revision of S3-254298 |
Huawei, HiSilicon | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254609 | Update solution #1.3 in TR 33.777 |
pCR revision of S3-254492 |
OPPO | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254610 | Intermediate conclusion for KI#1 |
pCR revision of S3-254383 |
Xiaomi Communications | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254611 | KI#2 update |
pCR revision of S3-254321 |
Ericsson | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254612 | Add evaluation for solution #2.1 |
pCR revision of S3-254148 |
ZTE Corporation | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254613 | Update Solution#2.2 |
pCR revision of S3-254297 |
Huawei, HiSilicon | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254614 | pCR Privacy requirements for sensing |
pCR revision of S3-254129 |
NTT DOCOMO INC. | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254615 | pCR KI on active attacks |
pCR revision of S3-254130 |
NTT DOCOMO INC. | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254616 | pCR KI on passive unauthorized sensing |
pCR revision of S3-254131 |
NTT DOCOMO INC. | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254617 | Pseudo-CR for 33.518 on New TC on NRF access token request |
other revision of S3-254098 |
MITRE-FFRDC | SCAS_5GA |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | ||
| S3-254618 | Living document to TS 33.518 |
draftCR revision of S3-254312 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254619 | Pseudo-CR for 33.926 on new threat on verification of access token request |
other revision of S3-254099 |
MITRE-FFRDC | SCAS_5GA |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | ||
| S3-254620 | Living document to TR 33.926 |
draftCR revision of S3-254306 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254621 | pCR for 33.117 on unnecessary or insecure services / protocols |
other revision of S3-254214 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254622 | pCR for 33.117 on Restricted reachability of services |
other revision of S3-254215 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254623 | GSMA NESAS change to TS 33.117 |
other revision of S3-254255 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254624 | Living document to TS 33.117 |
draftCR revision of S3-254307 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254625 | pCR for 33.514 on UP security policy configuration for 5G LAN service |
other revision of S3-254217 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254626 | pCR for 33.514 on SUPI de-concealment protection schemes |
other revision of S3-254216 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254627 | living document to TS 33.514 |
draftCR revision of S3-254259 |
Huawei, HiSilicon, CAICT, China Telecom Corporation Ltd. | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254628 | living document to TS 33.513 |
draftCR revision of S3-254258 |
Huawei, HiSilicon, CAICT, China Telecom Corporation Ltd. | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254629 | Living document to TS 33.521 |
draftCR revision of S3-254314 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254630 | Update to TS 33.116 MME SCAS according to NESASG feedback |
draftCR revision of S3-254139 |
ZTE Corporation | SCAS_5GA | Rel-19 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254631 | Living document for TS 33.226 |
draftCR revision of S3-254219 |
BSI (DE), Montsecure | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254632 | Clean-up of 33.523 |
draftCR revision of S3-254220 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254633 | Living document to TS 33.511 |
draftCR revision of S3-254308 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254634 | Reply LS to GSMA NESASG on changes |
LS out LS is reply to GSMA NESASG LS To: GSMA NESASG revision of S3-254254 |
Huawei, HiSilicon | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254635 | pCR for 33.730 conclusion |
other revision of S3-254221 |
BSI (DE) | FS_SCAS_CP | Rel-20 |
S3-125 AI: 5.2.8 |
noted | [WTS] [JSN] | |
| S3-254636 | Network product class description for SCAS_Femto_SeGW |
draftCR revision of S3-254143 |
ZTE Corporation | SCAS_Femto_SeGW | Rel-20 |
S3-125 AI: 5.1.6 |
approved | [WTS] [JSN] | |
| S3-254637 | Test case related to topology hiding for SCAS_Femto_SeGW |
pCR revision of S3-254144 |
ZTE Corporation | 33.547 0.1.0 | SCAS_Femto_SeGW | Rel-20 |
S3-125 AI: 5.1.6 |
approved | [WTS] [JSN] |
| S3-254638 | Threat related to topology hiding for SCAS_Femto_SeGW |
draftCR revision of S3-254145 |
ZTE Corporation | SCAS_Femto_SeGW | Rel-20 |
S3-125 AI: 5.1.6 |
approved | [WTS] [JSN] | |
| S3-254639 | Pseudo-CR on evaluation update for solution #1 in MPQUIC |
pCR revision of S3-254498 |
Qualcomm Incorporated | 33.778 0.0.1 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
approved | [WTS] [JSN] |
| S3-254640 | Resolution of Editor’s Note for Home-routed Roaming in Solution #3 |
pCR revision of S3-254388 |
Xiaomi EV Technology | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
approved | [WTS] [JSN] |
| S3-254641 | Pseudo-CR on ENs resolution for solution 6.6 |
pCR revision of S3-254086 |
Nokia | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
approved | [WTS] [JSN] |
| S3-254642 | Conclusion for Key Issue #1 |
pCR revision of S3-254042 |
InterDigital Finland Oy | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
noted | [WTS] [JSN] |
| S3-254643 | Conclusion for MPQUIC study | pCR | Ericsson | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
withdrawn | [WTS] [JSN] |
| S3-254644 | Adding scope |
pCR revision of S3-254304 |
Huawei, HiSilicon,ZTE | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
approved | [WTS] [JSN] |
| S3-254645 | pCR for 33.521 Clarification of Data Masking |
other revision of S3-254218 |
BSI (DE) | SCAS_5GA | Rel-20 |
S3-125 AI: 5.1.3 |
approved | [WTS] [JSN] | |
| S3-254646 | Update on Annex B: Mapping of Solutions to Key Issues |
pCR revision of S3-254206 |
vivo, Qualcomm | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-254647 | Pseudo-CR on System overview for the Attacker model |
pCR revision of S3-254413 |
Ericsson | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-254648 | Update to Security Area #1 |
pCR revision of S3-254509 |
Qualcomm Incorporated | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254649 | Pseudo-CR on Security Area: UE to Core Network security, security anchor |
pCR revision of S3-254411 |
Ericsson | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254650 | Updating access-agnostic authentication in Security area #3 |
pCR revision of S3-254527 |
CableLabs, Charter Communications, China Telecom, ZTE | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-254651 | Update Security area #3 for adding secondary authentication |
pCR revision of S3-254518 |
CATT | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-254652 | New Security Area - Security Architecture |
pCR revision of S3-254320 |
Huawei, HiSilicon | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-254653 | New Security Area on Security for Core Network, Interconnect and Roaming |
pCR revision of S3-254512 |
Nokia, Ericsson, Samsung | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-254654 | 6G new security area: exposure security |
pCR revision of S3-254104 |
Ericsson, Xiaomi, Nokia | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-254655 | Pseudo-CR on key issue related to MAC layer risk mitigation |
pCR revision of S3-254478 |
Ericsson | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
approved | [WTS] [JSN] |
| S3-254656 | New Security Area on Data collection for security monitoring |
pCR revision of S3-254412 |
Ericsson, AT&T, Lenovo, MITRE, Motorola Mobility, NSA, TMO US | 33.801-01 0.1.0 | FS_6G_SEC | Rel-20 |
S3-125 AI: 5.3.1 |
noted | [WTS] [JSN] |
| S3-254657 | Overview and Assumption for AEAD |
pCR revision of S3-254417 |
vivo Mobile Communication Co., | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-254658 | New Key Issue on AEAD Keys |
pCR revision of S3-254210 |
vivo, THALES | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-254659 | Pseudo-CR on KI#1 update |
pCR revision of S3-254082 |
KDDI Corporation | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-254660 | Requirement for AEAD interface |
pCR revision of S3-254105 |
Ericsson | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-254661 | Solution proposal AEAD algo selection for NAS and AS |
pCR revision of S3-254062 |
Nokia | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-254662 | Pseudo-CR on new solution for algorithm selection |
pCR revision of S3-254084 |
KDDI Corporation | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-254663 | Solution to KI#1 |
pCR revision of S3-254159 |
ZTE Corporation | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-254664 | New Solution on AEAD Algorithm Selection |
pCR revision of S3-254207 |
vivo | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-254665 | New solution on the AEAD algorithm negoiation |
pCR revision of S3-254272 |
Huawei, HiSilicon | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-254666 | New solution for AEAD algorithms negotiation |
pCR revision of S3-254373 |
Beijing Xiaomi Mobile Software | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-254667 | Solution proposal AEAD key usage for NAS and AS algorithm |
pCR revision of S3-254064 |
Nokia | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-254668 | Pseudo-CR on new solution for KI#2 interface |
pCR revision of S3-254085 |
KDDI Corporation | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-254669 | New solution on the details of AEAD interface |
pCR revision of S3-254271 |
Huawei, HiSilicon | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-254670 | New solution about creation of EXTRA_IV |
pCR revision of S3-254275 |
Huawei, HiSilicon | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-254671 | Solution proposal Key Hierarchy for NAS and AS AEAD |
pCR revision of S3-254065 |
Nokia | 33.771 0.1.0 | FS_AEAD | Rel-20 |
S3-125 AI: 5.3.2 |
approved | [WTS] [JSN] |
| S3-254672 | pCR to TS 33.502 - Example of trust domain |
pCR revision of S3-254124 |
Vodafone, China Mobile, AT&T, T-Mobile US, Verizon, Charter Communication, KDDI, Telecom Italia | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-254673 | pCR to TS 33.502 – EN resolving on configuration |
pCR revision of S3-254126 |
Vodafone, Verizon | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-254674 | Pseudo-CR on Prevention of DoS attacks on the Security related events collection entity |
pCR revision of S3-254406 |
Ericsson | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-254675 | pCR to TS 33.502 – Addressing NOTE on delivery |
pCR revision of S3-254128 |
Vodafone, Verizon | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-254676 | Pseudo-CR on Security events related to authentication failure |
pCR revision of S3-254405 |
Ericsson | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-254677 | pCR to TS 33.502 – Flooding Event |
pCR revision of S3-254119 |
Vodafone, Verizon | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-254678 | Replayed messages on SBA layer |
pCR revision of S3-254132 |
Johns Hopkins University APL | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
noted | [WTS] [JSN] |
| S3-254679 | pCR to TS 33.502 – Detecting SBA layer parameters change |
pCR revision of S3-254490 |
Vodafone | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-254680 | pCR to TS 33.502 – Protection for delivery of events |
pCR revision of S3-254120 |
Vodafone, AT&T, China Mobile, T-Mobile USA, Verizon, Telecom Italia, NTT DOCOMO, KDDI, Charter Communications | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-254681 | pCR to TS 33.502 – Protection for configuration of events |
pCR revision of S3-254121 |
Vodafone, T-Mobile US, AT&T, China Mobile, Verizon, Charter Communications, Telecom Italia, KDDI, NTT DOCOMO | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-254682 | pCR to TS 33.502 – Addressing ENs in clause 6 |
pCR revision of S3-254432 |
Vodafone | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
approved | [WTS] [JSN] |
| S3-254683 | Adding a NOTE for clarification regarding security related events |
pCR revision of S3-254167 |
Nokia | 33.502 0.2.0 | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
noted | [WTS] [JSN] |
| S3-254684 | Updates to Key Issue#5 |
pCR revision of S3-254171 |
Nokia | 33.746 0.2.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.13 |
approved | [WTS] [JSN] |
| S3-254685 | Evaluation for Solution for security of Local UPF for key issue 2 |
pCR revision of S3-254074 |
Nokia | 33.746 0.2.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.13 |
approved | [WTS] [JSN] |
| S3-254686 | EN Removal for Solution for detection of compromised Femto |
pCR revision of S3-254075 |
Nokia | 33.746 0.2.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.13 |
approved | [WTS] [JSN] |
| S3-254687 | Update the solution #1 |
pCR revision of S3-254172 |
China Telecom Corporation Ltd. | 33.746 0.2.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.13 |
approved | [WTS] [JSN] |
| S3-254688 | New solution to KI#4 |
pCR revision of S3-254161 |
ZTE Corporation | 33.746 0.2.0 | FS_NR_Femto_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.13 |
approved | [WTS] [JSN] |
| S3-254689 | Network product class description for SCAS_NR_Femto |
draftCR revision of S3-254141 |
ZTE Corporation | SCAS_NR_Femto | Rel-20 |
S3-125 AI: 5.1.5 |
approved | [WTS] [JSN] | |
| S3-254690 | Critical assests for SCAS_NR_Femto |
draftCR revision of S3-254142 |
ZTE Corporation | SCAS_NR_Femto | Rel-20 |
S3-125 AI: 5.1.5 |
approved | [WTS] [JSN] | |
| S3-254691 | Update Annex with NR Femto authentication threat in TR 33.926 |
other revision of S3-254430 |
China mobile |
S3-125 AI: 5.1.5 |
approved | [WTS] [JSN] | |||
| S3-254692 | Pseudo-CR-Add test case for device authentication in TS 33.546 |
pCR revision of S3-254394 |
China Mobile Com. Corporation | 33.546 0.1.0 | SCAS_NR_Femto | Rel-20 |
S3-125 AI: 5.1.5 |
approved | [WTS] [JSN] |
| S3-254693 | Pseudo-CR-Add test case for Hosting party authentication of TS 33.546 |
pCR revision of S3-254359 |
China Mobile Com. Corporation | 33.546 0.1.0 | SCAS_NR_Femto | Rel-20 |
S3-125 AI: 5.1.5 |
approved | [WTS] [JSN] |
| S3-254694 | Scope of TR 33.714 |
pCR revision of S3-254335 |
THALES | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-254695 | New solution: communication protection |
pCR revision of S3-254198 |
vivo | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-254696 | solution on information protection for DO-A capable AIOT device |
pCR revision of S3-254270 |
Huawei, HiSilicon | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-254697 | new Solution on Protecting Information |
pCR revision of S3-254489 |
OPPO | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-254698 | Update KI on AIOT device ID protection in DO-A procedure |
pCR revision of S3-254462 |
OPPO | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-254699 | New solution: privacy protection |
pCR revision of S3-254199 |
vivo | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-254700 | New Solution for privacy-presserving responses from individual devices to group paging |
pCR revision of S3-254364 |
Ericsson | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-254701 | New Solution for group paging in a privacy preserving manner |
pCR revision of S3-254363 |
Ericsson | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-254702 | DO-A Capable AIoT device identifier protection with Bloom filter |
pCR revision of S3-254434 |
Xidian University, OPPO | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-254703 | KI #4: solution for DO-A capable AIoT devices |
pCR revision of S3-254516 |
THALES | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-254704 | LS on scope alignment on AioT rel-20 |
LS out LS To: SA2,RAN2 revised to S3-254759 |
OPPO |
S3-125 AI: 5.2.11 |
revised | [WTS] [JSN] | |||
| S3-254705 | KI#2 |
pCR revision of S3-254336 |
THALES | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-254706 | KI1: security threats and requirements |
pCR revision of S3-254422 |
Nokia | 33.714 0.1.0 | FS_AIoT_SEC_Ph2 | Rel-20 |
S3-125 AI: 5.2.11 |
approved | [WTS] [JSN] |
| S3-254707 | Solution for Detection of compromised MWAB nodes |
pCR revision of S3-254073 |
Nokia | 33.724 0.1.0 | FS_5G_WAB_SEC | Rel-20 |
S3-125 AI: 5.2.14 |
noted | [WTS] [JSN] |
| S3-254708 | Update to SA3-LI ToR |
ToR revision of S3-254351 |
SA3-LI Chair |
S3-125 AI: 2.2 |
agreed | [WTS] [JSN] | |||
| S3-254709 | Reply LS on integrity failure |
LS out LS is reply to S3-254009 source LS: R2-2507915 LS To: RAN2 revision of S3-254547 |
Beijing Xiaomi Mobile Software | Rel-19 |
S3-125 AI: 3 |
approved | [WTS] [JSN] | ||
| S3-254710 | Pseudo-CR on BCP for access token privilege restriction |
pCR revision of S3-254410 |
Ericsson, Nokia, Nokia Shanghai Bell | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-254711 | BSP4SBA Clause 2.2 Token replay prevention (RFC 9700) |
pCR revision of S3-254285 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-254712 | BSP4SBA Clause 2.5 Client Authentication (RFC 9700) |
pCR revision of S3-254286 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-254713 | Overall pCR for not applicable Best practice RFC 9700 |
pCR revision of S3-254317 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-254714 | BSP4SBA Clause 3.2 Use Appropriate Algorithms (RFC 8725) |
pCR revision of S3-254287 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-254715 | BSP4SBA Clause 3.10 Do Not Trust Received Claims (RFC 8725) |
pCR revision of S3-254289 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-254716 | BSP4SBA Clause 3.11 Use Explicit Typing (RFC 8725) |
pCR revision of S3-254292 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-254717 | BSP4SBA Clause 3.8 Validate Issuer and Subject (RFC 8725) |
pCR revision of S3-254293 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-254718 | BSP4SBA Clause 3.9 Use and Validate Audience (RFC 8725) |
pCR revision of S3-254294 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-254719 | Overall pCR for not applicable Best practice RFC 8725 |
pCR revision of S3-254291 |
Huawei, HiSilicon | 33.755 0.1.0 | FS_BSP4SBA | Rel-20 |
S3-125 AI: 5.2.12 |
approved | [WTS] [JSN] |
| S3-254720 | Reply LS on Security parameter in A-IoT paging |
LS out LS is reply to S3-254010 LS To: RAN2 revision of S3-254420 |
Nokia | AmbientIoT-SEC | Rel-20 |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |
| S3-254721 | Rel-19 Corrections for IMS Data Channels and LI |
CR revision of S3-254398 |
Ericsson | 33.328 19.1.0 CR#891 catF | NG_RTC_SEC_Ph2 | Rel-19 |
S3-125 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-254722 | New sol on KI#1 |
pCR revision of S3-254163 |
China Telecom Corporation Ltd. | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-254723 | Group authorization for UE-deployed API invoker accessing other UEs' resources of a group |
pCR revision of S3-254455 |
Samsung | 33.700-23 0.1.0 | FS_CAPIF_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2. |
approved | [WTS] [JSN] |
| S3-254724 | AIoT correction to the authentication procedures |
CR revision of S3-254186 |
OPPO, CATT, InterDigital, vivo, [Huawei, HiSilicon, Lenovo, Ericsson, Qualcomm | 33.369 19.0.0 CR#174 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254725 | Addressing the missing information on the initial value of temporary identifier in Clause 5.4.3 and Annex B. |
CR revision of S3-254357 |
Lenovo [Ericsson] | 33.369 19.0.0 CR#553 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
not pursued | [WTS] [JSN] |
| S3-254726 | update T-ID in annex B and scope |
CR revision of S3-254138 |
ZTE | 33.369 19.0.0 CR#581 catF | AmbientIoT-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254727 | Initial high-level Conclusion |
pCR revision of S3-254328 |
Lenovo, Motorola Mobility | 33.786 0.2.0 | FS_AIMLE_SEC | Rel-20 |
S3-125 AI: 5.2.3 |
approved | [WTS] [JSN] |
| S3-254728 | Solution for PQC based SUCI Computation |
pCR revision of S3-254330 |
Lenovo, Motorola Mobility | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-254729 | Solution for Hybrid PQC based SUCI Computation | pCR | Lenovo, Motorola Mobility | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
withdrawn | [WTS] [JSN] |
| S3-254730 | Terminology Correction |
CR revision of S3-254241 |
Lenovo | 33.501 19.4.0 CR#22021 catF | XRM_Ph2-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254731 | Updating TLS1.2 and TLS1.3 to include EAP-TTLS and OAuth protocols |
pCR revision of S3-254179 |
Huawei, HiSilicon | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-254732 | Updating PKI to include OCSP protocol |
pCR revision of S3-254180 |
Huawei, HiSilicon | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-254733 | Pseudo-CR on Mission Critical PQ options |
pCR revision of S3-254051 |
NCSC, Motorola Solutions, BT, DSIT, NPL | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-254734 | Adding general description to 4.2.2 |
pCR revision of S3-254520 |
CATT | 33.547 0.1.0 | SCAS_Femto_SeGW | Rel-20 |
S3-125 AI: 5.1.6 |
approved | [WTS] [JSN] |
| S3-254735 | Living document TR 33.926 | draftCR | CATT | SCAS_Femto_SeGW | Rel-20 |
S3-125 AI: 5.1.6 |
approved | [WTS] [JSN] | |
| S3-254736 | Symmetric solution on SUCI protection |
pCR revision of S3-254193 |
vivo | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-254737 | Evaluation of solution #9 |
pCR revision of S3-254348 |
THALES, ORANGE | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254738 | Evaluation of solution #10 |
pCR revision of S3-254349 |
THALES, ORANGE | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
not treated | [WTS] [JSN] |
| S3-254739 | pCR to merge all Hybrid solutions together | pCR | Samsung | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
withdrawn | [WTS] [JSN] |
| S3-254740 | Reply to: LS on User consent for Data collection at the UE for NW-side model training |
LS out LS is reply to S3-254024 LS To: RAN2,RAN3 revision of S3-254548 |
NTT-Docomo |
S3-125 AI: 3 |
noted | [WTS] [JSN] | |||
| S3-254741 | Removal of Editors Notes |
CR revision of S3-254239 |
Lenovo, Ericsson, Nokia | 33.501 19.4.0 CR#22011 catF | XRM_Ph2-SEC | Rel-19 |
S3-125 AI: 4.1.1 |
agreed | [WTS] [JSN] |
| S3-254742 | PRINS Refinement on Trust Anchoring |
CR revision of S3-254050 |
BSI (DE) | 33.501 19.4.0 CR#21991 catB | RefinePRINS | Rel-20 |
S3-125 AI: 5.1.4 |
agreed | [WTS] [JSN] |
| S3-254743 | Adding technical baseline text in TS 33.546 |
pCR revision of S3-254322 |
China Unicom | 33.546 0.1.0 | SCAS_NR_Femto | Rel-20 |
S3-125 AI: 5.1.5 |
approved | [WTS] [JSN] |
| S3-254744 | Living document TR 33.926 | draftCR | China Unicom | SCAS_NR_Femto | Rel-20 |
S3-125 AI: 5.1.5 |
approved | [WTS] [JSN] | |
| S3-254745 | Solution proposal Hybrid SUCI calculation |
pCR revision of S3-254058 |
Nokia | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-254746 | Solution proposal Symmetric key SUCI |
pCR revision of S3-254060 |
Nokia | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-254747 | Update to Solution #2 | pCR | Xiaomi EV Technology | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
withdrawn | [WTS] [JSN] |
| S3-254748 | Resolution of Editor’s Note for Key Update in Solution #3 | pCR | Xiaomi EV Technology | 33.778 0.1.0 | FS_PSK_MQC_TLS | Rel-20 |
S3-125 AI: 5.2.5 |
withdrawn | [WTS] [JSN] |
| S3-254749 | New solution to SUCI calculation with symmetric key |
pCR revision of S3-254245 |
Lenovo | 33.703 0.2.0 | FS_CryptoPQC | Rel-20 |
S3-125 AI: 5.2.1 |
approved | [WTS] [JSN] |
| S3-254750 | pseudo-CR on authorization of sensing service request solution |
pCR revision of S3-254076 |
Nokia, Nokia Shanghai Bell | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254751 | Add evaluation for solution #1.1 |
pCR revision of S3-254147 |
ZTE Corporation | 33.777 0.2.0 | FS_Sensing_SEC | Rel-20 |
S3-125 AI: 5.2.7 |
approved | [WTS] [JSN] |
| S3-254752 | Resolve EN in Solution #1 |
pCR revision of S3-254154 |
ZTE Corporation | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-254753 | Add evaluation for solution #1 |
pCR revision of S3-254152 |
ZTE Corporation | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-254754 | Address the ENs in solution #5 |
pCR revision of S3-254371 |
Beijing Xiaomi Mobile Software | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-254755 | Address ENs in Sol#6 of TR 33.700-30 |
pCR revision of S3-254283 |
Huawei, HiSilicon, Samsung | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-254756 | Add evaluation in Sol#6 of TR 33.700-30 |
pCR revision of S3-254279 |
Huawei, HiSilicon, Samsung | 33.700-30 0.1.0 | FS_5GSAT_Ph4_SEC | Rel-20 |
S3-125 AI: 5.2.9 |
approved | [WTS] [JSN] |
| S3-254757 | New WID on Security related Events Handling |
WID revised revision of S3-254463 |
Vodafone | SECHAND | Rel-20 |
S3-125 AI: 6.3 |
agreed | [WTS] [JSN] | |
| S3-254758 | Cover sheet 33.502 for information | TS or TR cover | Vodafone | SECHAND | Rel-20 |
S3-125 AI: 5.1.1 |
approved | [WTS] [JSN] | |
| S3-254759 | LS on scope alignment on AioT rel-20 |
LS out LS To: SA2,RAN2 revision of S3-254704 |
OPPO |
S3-125 AI: 5.2.11 |
approved | [WTS] [JSN] |
760 documents (1.2743861675262 seconds)