TDoc | Title | Source |
---|---|---|
S3-251810 | Agenda | SA WG3 Chair |
S3-251812 | Process for SA3#122 | SA WG3 Chair |
S3-251813 | Detailed agenda planning | SA WG3 Chair |
TDoc | Title | Source |
---|---|---|
S3-251811 | Report from SA3#121 | MCC |
S3-252105 | Report from SA3#121 | MCC |
TDoc | Title | Source |
---|---|---|
S3-251815 | LS on Device Subscription Data | S2-2501242 |
S3-251816 | Reply to LS on IMS support for AF authorization and IMS avatar communication | S2-2502434 |
S3-251817 | LS on the scope attribute of the access token standard claims | S5-251112 |
S3-251818 | Reply LS on secure storage and processing of credentials for AIoT | ETSI TC SET |
S3-251819 | Reply LS on including the HPLMN ID in the PC5 discovery messages for 5G ProSe UE-to-UE relay | C1-252256 |
S3-251820 | LS on feedback for IMS resiliency study | C4-251492 |
S3-251821 | LS to 3GPP SA3 re Adoption of TS 33.520, 33.528, 33.529, 33.530 and 33.537 as NESAS SCASes | GSMA |
S3-251822 | LS on AI/ML UE sided data collection | R2-2503168 |
S3-251823 | Reply LS on signalling feasibility of dataset and parameter sharing | R2-2503169 |
S3-251824 | Reply LS for Reply LS on security handling for inter-CU LTM in non-DC cases | R3-252449 |
S3-251825 | Reply LS on Privacy and security aspects regarding DC management by the network | S2-2504207 |
S3-251826 | LS on AIoT device identifier length | S2-2504296 |
S3-251827 | Reply LS on OSAppID usage by AppToken use case | S2-2504468 |
S3-251828 | LS on Management of secure backhaul for NTN | S5-251990 |
S3-251830 | LS on LP-WUS subgrouping progress | R2-2503182 |
S3-251832 | LS on Towards a common definition of Zero Trust | ITU-T Study Group 17 |
S3-251833 | LS on Avatar Security Aspects | S4-250715 |
S3-251837 | TCG progress - report from TCG rapporteur | InterDigital Finland |
S3-251839 | LS on establishment of a new work item Technical Report ITU-T TR.FMSC-IMT2030 “Security technologies of fixed, mobile and satellite convergence for IMT-2030 networks” | ITU-T SG17 |
S3-251840 | LS on the establishment of a new work item ITU-T X.s-isac “Security guidelines for integrated sensing and communication in IMT-2020 networks and beyond” | ITU-T SG17 |
S3-251841 | LS on the establishment of a new work item ITU-T X.uc-zt-5g “Security threats associated with use cases for applying zero trust to IMT-2020 private network deployments” | ITU-T SG17 |
S3-251842 | O-RAN ALLIANCE – 3GPP collaboration on PQC | O-RAN |
S3-251843 | LS on LI requirements on IMS Data Channel | s3i250185 |
S3-251898 | LS on Avatar Security Aspects | Nokia, Nokia Shanghai Bell |
S3-251963 | LS reply on Avatar Security Aspects | CATT |
S3-251968 | Reply LS to SA5 on token scope | Huawei, HiSilicon |
S3-251969 | Reply LS on Management of secure backhaul for NTN | Huawei, HiSilicon |
S3-251970 | Reply LS on 3GPP collaboration on PQC | Huawei, HiSilicon |
S3-251992 | reply LS on Device Subscription Data | Huawei, HiSilicon |
S3-252034 | Reply to: Reply LS on secure storage and processing of credentials for AIoT | Nokia |
S3-252035 | LS reply on Device Subscription Data | Nokia |
S3-252107 | Reply LS on Avatar Security Aspects | Huawei, HiSilicon |
S3-252108 | Reply LS on authorization and authentication in Avatar communication | Huawei, HiSilicon |
S3-252114 | Reply LS on adoption of newly published 3GPP SCASes | Huawei, HiSilicon |
S3-252116 | Solving issues to TS 33.529 according to LS from GSMA NESASG | Huawei, HiSilicon |
S3-252185 | LS on USS changeover procedure | Ericsson |
S3-252225 | LS reply on a common definition of Zero Trust | MITRE-FFRDC |
TDoc | Title | Source |
---|---|---|
S3-251831 | Reply LS to S3-251226 LS on the scope attribute of the access token standard claims | Nokia |
S3-252255 | Update proposal to S3-251831 | Nokia |
TDoc | Title | Source |
---|---|---|
S3-251834 | Living document for TEI19: Token-based authorization for indirect communication scenarios when NF is selected at target PLMN | Ericsson, Nokia, Nokia Shanghai Bell |
S3-251835 | Token-based authorization for indirect communication scenarios when NF is selected at target PLMN | Ericsson, Nokia |
S3-252139 | Discussion on the NF consumer PLMN ID check | Ericsson |
S3-252140 | Checking PLMNID of NF Service Consumer in interconnect scenario | Ericsson, Nokia Nokia Shanghai Bell |
S3-252141 | Checking PLMNID of NF Service Consumer in interconnect scenario | Ericsson, Nokia, Nokia Shanghai Bell |
S3-252142 | Checking PLMNID of NF Service Consumer in interconnect scenario | Ericsson, Nokia, Nokia Shanghai Bell |
S3-252143 | LS on Checking PLMNID of NFc in interconnect scenario | Ericsson |
S3-252144 | LS on PLMN ID checks in interconnect scenarios when NFc supports multiple PLMN IDs | Ericsson |
S3-252237 | Implementation correction of CR2040 | Nokia |
S3-252254 | Clarification on verification of NFc for discovery in roaming scenario | MITRE-FFRDC |
TDoc | Title | Source |
---|---|---|
S3-251934 | Add clause 6.3 in the Kaf derivation descriptions - R17 | ZTE |
S3-251935 | Add clause 6.3 in the Kaf derivation descriptions - R18Mirror | ZTE |
S3-252014 | Update service disabling procedure | China Mobile, ZTE |
TDoc | Title | Source |
---|---|---|
S3-251936 | update to AKMA based mechanism | ZTE Corporation |
TDoc | Title | Source |
---|---|---|
S3-251872 | ZUC number of initialisation rounds | Nokia |
S3-251884 | Correction to f5** description | Thales, Ericsson |
S3-251889 | AIMLE Security Alignment | Lenovo |
S3-251998 | Clarification for CMP over TLS | Huawei, HiSilicon |
S3-251999 | Clarification for certificate lifecycle management | Huawei, HiSilicon |
S3-252000 | Discussion paper for certificate lifecycle management | Huawei, HiSilicon |
S3-252002 | Clarification for CMP over TLS | Huawei, HiSilicon |
S3-252101 | Removal of the terminology “AS root key” | Apple, NTT DOCOMO, Qualcomm Incorporated |
S3-252145 | New JWS profiles for CCA tokens and access tokens | Ericsson |
S3-252155 | Fix issues on SEAL security framework | Nokia, Nokia Shanghai Bell |
S3-252180 | Correcting inconsistencies to clause 6.2.3 of 33.210 | Qualcomm Incorporated |
S3-252183 | Multiple Editorial corrections | Nokia |
S3-252184 | Multiple Editorial correction | Nokia |
S3-252189 | Making NF type as pre-registered parameter in CA/RA for IAK method | Ericsson |
S3-252211 | Issues about user consent for exposure and a proposal to address them | Ericsson |
S3-252212 | Clarification of the intended applicability and requirements for Annex V | Ericsson |
S3-252220 | Clarification on client credential flow – Rel-18 | Ericsson |
S3-252221 | Clarification on client credential flow | Ericsson |
S3-252230 | Clarification on naming of purposes for user consent | Nanjing vivo Software Tech. |
TDoc | Title | Source |
---|---|---|
S3-251866 | [33.180] Alignment of Logging Recording and Audit | Airbus |
S3-252008 | Clarification about security for MC over IOPS | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
S3-251844 | Add a new clause in annexure to Security Assurance Specification (SCAS) threats and critical assets in 3GPP network product classes specific to SMSF | MCC |
S3-251846 | Minor editorial corrections and clean-up | IIT Bombay |
S3-251847 | Correction of test names and clean up of 33.117 | BSI (DE) |
S3-251848 | Clean up and correction of test names in 33.216 | BSI (DE) |
S3-251849 | Addition of test names and Clean up of 33.511 | BSI (DE) |
S3-251850 | Correction of test names and clean up of 33.513 | BSI (DE) |
S3-251851 | Clean up of 33.514 | BSI (DE) |
S3-251852 | Correction of test names and clean up of 33.515 | BSI (DE) |
S3-251853 | Addition of test name and clean up of 33.517 | BSI (DE) |
S3-251854 | Clean up of 33.523 | BSI (DE) |
S3-251855 | Clean up of 33.527 and correction of test names | BSI (DE) |
S3-251856 | Clean up of 33.529 | BSI (DE) |
S3-251857 | Correction of test case and clean up of 33.512 | BSI (DE) |
S3-251858 | Living Document to 33.512 AMF | BSI (DE), Montsecure |
S3-251867 | Minor editorial modification | IIT Bombay |
S3-251899 | Wrong test steps for IPSec testing in N2/Xn | Keysight Technologies UK Ltd |
S3-251924 | Correction of TC on replay protection | MITRE-FFRDC |
S3-251937 | Add PCAP traces in clause 4.2.2.1 | ZTE |
S3-252119 | Solving the improvement point to TS 33.537 according to LS from GSMA NESASG | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
S3-251836 | Living document for TEI19: Public key distribution and Issuer claim verification of the Access Token | Ericsson, Nokia, Nokia Shanghai Bell, NCSC |
S3-252001 | Discussion paper of the certificate identifier for public key distribution | Huawei, HiSilicon |
S3-252146 | Public key distribution service support both raw key and certificate | Ericsson, NCSC, KDDI, AT&T, BT, Deutsche Telekom, Huawei, Samsung |
S3-252147 | OAuth Tokens for NF Type level access | Ericsson, NCSC |
S3-252148 | WID on Public key distribution and Issuer claim verification of the Access Token | Ericsson, NCSC, Huawei, AT&T, Deutsche Telekom, BT |
S3-252229 | Updates to key retrieval service | Nokia |
TDoc | Title | Source |
---|---|---|
S3-251930 | Security mechanism and procedures for inter-CU LTM in non-DC | OPPO |
S3-251938 | Update conclusion for KI#1 | ZTE Corporation |
S3-251939 | Update security machanism and procedures for inter-CU LTM | ZTE Corporation |
S3-251988 | Updates for the handling of mismatched UE security context handling in non-DC cases | Huawei, HiSilicon |
S3-251989 | Updates for the NCC transmission in LTM procedure | Huawei, HiSilicon |
S3-251990 | security handling where CU is acting as MN and SN is unchanged | Huawei, HiSilicon |
S3-251991 | Reply LS on security handling for inter-CU LTM in non-DC cases | Huawei, HiSilicon |
S3-252017 | Procedure for security handling for LTM | vivo |
S3-252053 | Living document on NR mobility enhancement | Samsung |
S3-252054 | Security procedure for inter-CU LTM | Samsung |
S3-252070 | Reply LS on security handling for inter-CU LTM in non-DC cases | Xiaomi EV Technology |
S3-252071 | Security Handling for inter-CU LTM | Xiaomi EV Technology |
S3-252103 | LTM - Conclusions | Apple |
S3-252104 | LTM - Security procedures | Apple |
S3-252187 | Security mechanism and procedure for inter-CU-LTM | LG Electronics |
S3-252188 | Conclusion update for Key issue #1 | LG Electronics |
TDoc | Title | Source |
---|---|---|
S3-252009 | Fix the figures of CP-based multi-hop U2NW link setup | Huawei, HiSilicon |
S3-252010 | Clarification and editorial for multi-hop Relay scenarios | Huawei, HiSilicon |
S3-252131 | Discussion paper on security of ProSe in SNPN | China Telecom Corporation Ltd.,Nokia, Nokia Shanghai Bell |
S3-252132 | Add note for security of prose in npns | China Telecom, Nokia, Nokia Shanghai Bell |
S3-252171 | Addressing the Editor’s Notes in multi-hop U2N relay discovery security | Qualcomm Incorporated, Huawei, HiSilicon, China Telecom, Beijing Xiaomi, InterDigital |
TDoc | Title | Source |
---|---|---|
S3-252011 | Clarification to clause 4.1 | Huawei, Hisilicon,Nokia, ZTE |
TDoc | Title | Source |
---|---|---|
S3-251863 | Living document for Automatic Certificate Management Environment (ACME) for the Service Based Architecture (SBA) | Cisco Systems, Huawei, US National Security Agency, Charter Communications, Google, Johns Hopkins University APL |
S3-251901 | IANA registrations | Cisco Systems |
S3-251902 | Acquiring an authority token | Cisco Systems |
TDoc | Title | Source |
---|---|---|
S3-251903 | Security Environment, Living document for security aspects of 5G satellite access phase 3 | InterDigital Finland Oy, Samsung, T-Mobile USA |
S3-251964 | A summary report from offline calls for Rel-19 WI on 5GSAT_Ph3_SEC | Nokia |
S3-252007 | Resolving EN in Annex of split MME by implementation | Huawei, HiSilicon |
S3-252043 | DoS attack remediation in S&F operation | Samsung, Johns Hopkins University Applied Physics Lab, Philips, Intel, Interdigital |
S3-252080 | Addressing EN in store and forward satellite operation | Xiaomi Technology |
S3-252106 | Living document to TS 33.401 for adding abbreviations and definitions | Huawei, HiSilicon |
S3-252110 | Update the Security aspects of Full EPC in each satellite | China Telecom Corporation Ltd. |
S3-252117 | Discussion on resolving EN in annex of Split MME by implementation | Huawei, HiSilicon |
S3-252118 | Living document for security aspects of 5G satellite access phase 3 | CATT |
S3-252120 | Remove the EN about DDoS attack | China Telecom Corporation Ltd. |
S3-252122 | Way forward for DoS attack topic | CATT |
S3-252126 | Update security aspects of Split MME architecture | CATT |
S3-252127 | Update security aspects of Full EPC in each satellite | CATT |
S3-252156 | Removing normative phrasing by referring to SA2 text | Qualcomm Incorporated |
S3-252157 | Proposal for DDoS editor’s note resolution | Qualcomm Incorporated |
S3-252228 | pCR against living draft CR on S&F | THALES |
TDoc | Title | Source |
---|---|---|
S3-251971 | SA2 on UUAA during USS changeover | Huawei, HiSilicon |
S3-252055 | Adding support for multiple USSs | Qualcomm Incorporated, InterDigital, Ericsson, Huawei |
TDoc | Title | Source |
---|---|---|
S3-251940 | resolving EN for Authentication and authorization for digital asset services | ZTE Corporation |
S3-251941 | resolving EN for Authentication and authorization for spatial localization services | ZTE Corporation |
S3-251942 | resolving EN for Privacy protection for user information exposure | ZTE Corporation |
S3-252036 | Living document on Metaverse_Sec | Samsung |
S3-252072 | Editor’s Note Resolution for Privacy Protection | Xiaomi EV Technology |
S3-252073 | Correction on the Authorization of DA services using CAPIF | Xiaomi EV Technology |
S3-252074 | Correction on the Authentication of Digital Representation using SEAL | Xiaomi EV Technology |
TDoc | Title | Source |
---|---|---|
S3-251845 | Living CR on Finer level authorization | Nokia, Huawei |
S3-251868 | Living CR on Nested API | Ericsson, Samsung, Xiaomi, Nokia |
S3-251869 | Living CR on Cross UE authorization | Xiaomi Communications |
S3-251870 | Living CR on RO authorization | Huawei, HiSilicon, Nokia, Xiaomi, Lenovo, CATT, China Telecom, Ericsson |
S3-251883 | Living CR for Onboarding API Invoker Residing in the UE | Lenovo, Nokia, Ericsson |
S3-251885 | Discussion paper on Security threats with Onboarding Procedure | Lenovo, Motorola Mobility, Nokia |
S3-251886 | Onboarding API Invoker Residing in the UE | Lenovo, Nokia |
S3-251887 | Updates to security procedure for CAPIF interconnection | Lenovo |
S3-251888 | Updates to Living CR on RO authorization | Lenovo |
S3-251890 | Living CR on Interconnection | Samsung, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson |
S3-251894 | Living CR on revocation | China Telecom Corporation Ltd. |
S3-251931 | Addition on revocation procedure | CATT |
S3-251932 | Updates to living Draft CR on CAPIF nested API | CATT |
S3-251933 | Updates to living Draft CR on RO authorization | CATT |
S3-251943 | pCR against draft CR on Authentication and Authorization for CAPIF RNAA interconnection | ZTE Corporation |
S3-251944 | resolving EN for Method 3 TLS with OAuth Token | ZTE Corporation |
S3-251945 | resolving EN for Resource Owner authentication revocation | ZTE Corporation |
S3-251959 | Baseline pCR against Draft CR for KI#1.2 on revocation | China Telecom Corporation Ltd. |
S3-251960 | KI#2 pCR on top of the baseline pCR- interconnect | China Telecom Corporation Ltd. |
S3-251972 | KI#1.2 update RO authorization to address EN | Huawei, HiSilicon, Nokia |
S3-251973 | KI#1.2 update revocation to address EN | Huawei, HiSilicon |
S3-251974 | KI#1.3 updating text for finer level authorization | Huawei, HiSilicon, Nokia |
S3-252037 | Updates to security procedure for CAPIF interconnection | Samsung, Xiaomi, China Telecom, Nokia, Nokia Shanghai Bell, Lenovo, CATT |
S3-252038 | Resolving EN on API invoker authentication during access token request | Samsung |
S3-252039 | pCR for authentication and authorization for RNAA in CAPIF interconnection scenario | Samsung |
S3-252040 | Resolving Editor's Note in Revocation clause | Samsung |
S3-252041 | pCR to update CAPIF nested API authorization procedure | Samsung |
S3-252075 | pCR against Living CR on Cross UE authorization | Xiaomi communications, Nokia |
S3-252076 | pCR against Living CR on revocation | Xiaomi communications |
S3-252077 | pCR against Living CR on RO management | Xiaomi communications |
S3-252078 | pCR against interconnection baseline | Xiaomi communications |
S3-252213 | Updates to the living CR on finer level authorization | Ericsson |
S3-252214 | Updates to the baseline document on CAPIF interconnection | Ericsson |
S3-252215 | Updates to the living CR on Cross UE authorization | Ericsson |
S3-252216 | Updates to the living CR on RO authorization | Ericsson |
S3-252217 | Updates to the living CR on Nested API | Ericsson |
S3-252218 | Updates to the living CR on Revocation | Ericsson |
S3-252219 | Clarification on resource owner ID in the token | Ericsson |
S3-252232 | Updates to Living CR on Finer level of authorization | Lenovo |
S3-252233 | Updates to Living CR on revocation | Lenovo |
S3-252247 | RO definition | Nokia, Lenovo |
S3-252248 | Update to S3-251845 on Finer level of authorization | Nokia |
S3-252249 | Update to S3-251848 on Nested API | Nokia |
S3-252250 | Update to S3-251870 on RO management | Nokia |
S3-252251 | Update to S3-251890 on CAPIF-interconnection | Nokia |
S3-252252 | Update to S3-251894 on revocation | Nokia |
TDoc | Title | Source |
---|---|---|
S3-252109 | Security of Avatar Communication | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
S3-252113 | Addressing EN for Data Channel Exposure | Huawei, HiSilicon |
S3-252115 | Changing DC to Data Channel | Huawei, HiSilicon |
S3-252199 | Living document for NG_RTC_SEC_Ph2: draftCR to TS 33.203, Signing and verification of third party user identity information in IMS | Ericsson |
S3-252200 | Signing and verification of third party user identity information in IMS | Ericsson |
S3-252201 | Proposal for a living document for NG_RTC_SEC_Ph2: draftCR to TS 33.328, Security of IMS avatar communication | Ericsson |
S3-252202 | Living document for NG_RTC_SEC_Ph2: draftCR to TS 33.328, Security and privacy of IMS capability exposure | Ericsson, Huawei, HiSilicon, China Mobile |
S3-252203 | Changes to the Living document for NG_RTC_SEC_Ph2: draftCR to TS 33.328, Security and privacy of IMS capability exposure | Ericsson |
TDoc | Title | Source |
---|---|---|
S3-251929 | Update security for data collection for the LMF-based AIML positioning | OPPO |
S3-251946 | Update figures of the living document for AIML_CN_SEC | ZTE Corporation |
S3-251962 | Alignment CR | Nokia |
S3-252003 | Various Editorial changes to the living CR | Huawei, HiSilicon |
S3-252004 | Update NEF security requirement for Secure NF Instance ID | Huawei, HiSilicon |
S3-252056 | Living document for AIML_CN_SEC | China Mobile, vivo,Huawei, HiSilicon,OPPO,Ericsson,Nokia, Xiaomi,ZTE, CATT |
S3-252057 | Editorial changes for Living document | China Mobile |
TDoc | Title | Source |
---|---|---|
S3-251984 | Security for PLMN hosting a NPN | China Telecom, ZTE |
TDoc | Title | Source |
---|---|---|
S3-251897 | Procedure for Protection of AIoT device identifier privacy | Sony, OPPO |
S3-251907 | AIoT authentication procedure based on stored nonces | KPN N.V. |
S3-251908 | AIoT baseline requirements | KPN N.V. |
S3-251914 | Pseudo-CR on AIoT temporary ID requirement | NTT DOCOMO INC. |
S3-251916 | LS on power and energy consumption budget for security features in AioT | ORANGE |
S3-251917 | AIoT - Subscription Credentials Storage and Processing | Orange Belgium |
S3-251918 | AIoT - Subscription Credentials Storage and Processing | Orange Belgium |
S3-251922 | Content to 4.2.2 requirement on the AIOTF | OPPO |
S3-251926 | Content to 4.2.1 requirement on the device | OPPO |
S3-251927 | Content to 5.5 protection between AIOT network elements | OPPO |
S3-251947 | Add a clause about requirement on AIoT Reader | ZTE Corporation |
S3-251948 | Update the clause 4.2.1 Requirements on the device | ZTE Corporation |
S3-251949 | Update the clause 4.2.2 Requirements on the AIOTF | ZTE Corporation |
S3-251950 | Update the clause 5.2 Authentication procedure | ZTE Corporation |
S3-251951 | Update the clause 5.3 | ZTE Corporation |
S3-251952 | Update the clause 5.5 Protection between AIoT network element | ZTE Corporation |
S3-251993 | Authentication procedure in AIoT service | Huawei, HiSilicon, Vivo |
S3-251994 | Security protection between AIoT network elements | Huawei, HiSilicon |
S3-252023 | Security requirements on the AIOTF | vivo |
S3-252024 | communication secuirty procedure | vivo |
S3-252025 | Clarification on X.12.2 | vivo |
S3-252031 | Proposal regarding AIOTF requirements. | Nokia |
S3-252032 | Proposal regarding AIOT device requirements. | Nokia |
S3-252033 | Proposal regarding ADM requirements. | Nokia |
S3-252051 | Security requirements on AIoT device | Samsung |
S3-252052 | Security requirements on AIoTF | Samsung |
S3-252061 | Update clause 5.1 of TS 33.369 | China Mobile |
S3-252062 | Update clause 4.1 of TS 33.369 | China Mobile |
S3-252063 | Update clause 4.2.2 of TS 33.369 | China Mobile |
S3-252064 | Update clause 5.4 of TS 33.369 | China Mobile |
S3-252067 | AIoT Authentication Procedure for Inventory | OPPO |
S3-252068 | AIoT authentication procedure for Command | OPPO |
S3-252081 | Security requirements on the AIoTF | Xiaomi Technology |
S3-252082 | Security requirements on the AIoT device | Xiaomi Technology |
S3-252083 | Authentication procedure for AIoT service | Xiaomi Technology |
S3-252084 | Protection of information during AIoT service communication | Xiaomi Technology |
S3-252086 | Discussion on AIoT security principles | CATT |
S3-252088 | pCR to TS33.369 Security requirements on the device | CATT |
S3-252089 | pCR to TS33.369 Security requirements on the AIOTF | CATT |
S3-252090 | pCR to TS33.369 Security requirements on the ADM | CATT |
S3-252091 | pCR to TS33.369 AIoT Device authentication procedure | CATT |
S3-252092 | pCR to TS33.369 AIoT Device communication security procedure | CATT |
S3-252093 | pCR to TS33.369 AIoT Device privacy protection | CATT |
S3-252094 | pCR to TS33.369 AIoT Device group privacy protection | CATT |
S3-252095 | AIoT TS - Security Requirements for AIoT devices | Apple |
S3-252096 | AIoT TS - Security Requirements for AIOTF | Apple |
S3-252097 | AIoT TS- Authentication - General clause | Apple |
S3-252098 | AIoT TS- Authentication procedure for Inventory | Apple |
S3-252125 | PCR on Protection of information during AIoT service communication | OPPO |
S3-252136 | Protection of AIoT data in command message | Huawei, HiSilicon |
S3-252137 | security requirement on device | Huawei, HiSilicon |
S3-252138 | Discussion paper on credential storage in Ambinet IoT device | Huawei, HiSilicon |
S3-252149 | Pseudo-CR on AIoT device security requirements related to cryptographic algorithms | Ericsson |
S3-252150 | AIoT Device Secure Storage | Ericsson |
S3-252151 | Pseudo-CR on Privacy for group paging | Ericsson |
S3-252158 | Discussion on issues in temporary ID based approaches and way forward proposal | Qualcomm Incorporated, Ericsson, Lenovo |
S3-252159 | Protection of AIoT device identifier privacy | Qualcomm Incorporated |
S3-252164 | Authentication procedures | Qualcomm Incorporated |
S3-252165 | Security procedure on the information protection in command procedure | Qualcomm Incorporated |
S3-252166 | Addressing EN in the requirements on the ADM | Qualcomm Incorporated |
S3-252167 | Storage and processing of credentials requirements on the device | Qualcomm Incorporated |
S3-252168 | Confidentiality and integrity protection requirements on device | Qualcomm Incorporated |
S3-252169 | Device security requirements regarding inventory with filtering information | Qualcomm Incorporated |
S3-252170 | AIoT specific key bootstrapping procedure | Qualcomm Incorporated |
S3-252208 | Handling of Temporary Identity for the initial Individual Inventory Request | Lenovo |
S3-252210 | Network assigned Temporary Group Identity | Lenovo |
S3-252227 | Credential storage requirement for device | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
S3-251865 | Selection of authentication mode for MRI in forwarded mode | Nokia |
S3-252121 | Addressing the EN on the concrete modes of AES for protecting XRM Media related information when using connect-UDP forwarded mode | Huawei, HiSilicon |
S3-252123 | Addressing the ENs of Key derivation, Nonce and counter values, and VCID uniqueness in the forwarding mode. | Huawei, HiSilicon |
S3-252124 | Addressing the EN on the length of the protected MRI content | Huawei, HiSilicon |
S3-252181 | Providing security details for forwarding mode in XRM | Ericsson |
S3-252182 | Comparison of AES-CCM, AES-GCM, and AES-GCM-SST for protection of XRM | Ericsson |
TDoc | Title | Source |
---|---|---|
S3-251913 | Avatar Identification and mapping within BAR | Vodafone Ireland Plc |
S3-252044 | Resolving EN in KI#2 conclusion | Samsung |
S3-252045 | Resolving EN related to impersonation | Samsung |
S3-252111 | Update conclusion of KI#2 | Huawei, HiSilicon |
S3-252112 | Addressing EN in conclusion of KI#3 | Huawei, HiSilicon |
S3-252193 | Conclusion update for KI#2: Security of IMS based Avatar Communication | Ericsson |
S3-252194 | Conclusion update for KI#3: Security and privacy aspects of IMS DC capability exposure | Ericsson |
S3-252195 | TR cleanup | Ericsson |
S3-252196 | Presentation of Specification/Report to TSG:\nTR 33.790 Study on the security support for the next generation real time communication services phase 2, Version 1.3.0 | Ericsson |
S3-252197 | Discussion about the LS on Avatar Security Aspects from SA4 | Ericsson |
S3-252198 | Reply LS on Avatar Security Aspects | Ericsson |
TDoc | Title | Source |
---|---|---|
S3-251895 | KI#3, New Merged Solution | Sony, OPPO |
S3-251896 | KI#3, Update Conclusions | Sony, OPPO |
S3-251906 | Pseudo-CR on Update AIOT sol#37 | Xidian University |
S3-251909 | Resolving ENs in Solution #42 | KPN N.V. |
S3-251915 | Update of KI#3 | NTT DOCOMO INC. |
S3-251919 | update AIOT KI#3 | OPPO |
S3-251920 | Update AIOT sol#24 | OPPO |
S3-251921 | Update AIOT conclusion#3 | OPPO |
S3-251923 | pCR to TR33.713 Remove EN in solution#9 | CATT |
S3-251925 | pCR to TR33.713 Remove EN in solution#30 | CATT |
S3-251953 | update sol#6 | ZTE Corporation |
S3-251954 | new solution to KI#3 | ZTE Corporation |
S3-251955 | resolving ENs in sol#25 in TR 33.713 | ZTE Corporation |
S3-251995 | removing the editor's note in solution 4 | Huawei, HiSilicon |
S3-252018 | New Sol KI#3, Combine UE-generated temp ID with network-assigned temp ID | vivo |
S3-252019 | Conclusion update on KI#3 for AIoT privacy | vivo |
S3-252020 | Remove EN for Sol#10 | vivo |
S3-252021 | Remove EN for Sol#40 | vivo |
S3-252022 | Remove EN for Sol#41 | vivo |
S3-252029 | Resolution of EN in solution 35 concerning device constrains | Nokia |
S3-252030 | Refinement of EN in KI#5 | Nokia |
S3-252046 | pCR on resolving EN on solution #22 | Samsung |
S3-252047 | pCR on evaluation update on solution #22 | Samsung |
S3-252048 | pCR on converting EN into NOTE in solution #22 | Samsung |
S3-252049 | pCR on resolving EN on solution #38 | Samsung |
S3-252050 | pCR on evaluation update on solution #38 | Samsung |
S3-252058 | Evaluation for Sol#45 in TR 33.713 | China Mobile |
S3-252059 | Resolve EN of sequence number of figure in Sol#45 in TR 33.713 | China Mobile |
S3-252060 | Resolve ENs in Sol#45 of TR 33.713 | China Mobile |
S3-252085 | Remove Editor’s Notes in solution 16 of TR 33.713 | Xiaomi Technology |
S3-252099 | AIoT TR - Clean up on the KI#3 | Apple |
S3-252100 | AIoT TR - Clean up on the KI#4 | Apple |
S3-252128 | Update AIoT conclusion #4 | OPPO |
S3-252129 | Update Solution #17 in TR 33.713 | OPPO |
S3-252130 | Remove ENs in Solution #32 and #33 | OPPO |
S3-252152 | Addressing EN in AIoT Solution #29 | Ericsson |
S3-252153 | Addressing EN in AIoT Solution #43 | Ericsson |
S3-252160 | Update on KI#3 conclusion | Qualcomm Incorporated |
S3-252161 | Proposed addition to general conclusion related to credential storage | Qualcomm Incorporated |
S3-252162 | Updates on solution 15 | Qualcomm Incorporated |
S3-252163 | Addressing ENs in solution 34 | Qualcomm Incorporated |
S3-252205 | General conclusion: network layer | THALES, ORANGE |
S3-252207 | General conclusion: security capabilities | THALES, ORANGE |
S3-252209 | General conclusion: authentication | THALES, ORANGE |
S3-252222 | Conclusion KI#5: credentials | THALES, ORANGE |
S3-252223 | Conclusion KI#5: authentication | THALES, ORANGE |
S3-252224 | Conclusion KI#5: solutions | THALES, ORANGE |
S3-252226 | Resolution of ENs in solution #39 | THALES |
S3-252231 | Resolution of ENs in solution #39 | THALES |
S3-252234 | Pseudo-CR Solution for KI#3: Paging with AIOT group ID | NTT DOCOMO INC. |
TDoc | Title | Source |
---|---|---|
S3-252239 | Miscellaneous updates in introductionary part | Xiaomi, Nokia |
S3-252240 | Missing clarifications and typos correction | Xiaomi, Nokia |
S3-252241 | Implementation of original figures | Xiaomi, Nokia |
S3-252242 | Solution 11 editorial updates | Nokia |
S3-252243 | Solution 13 figure update and FFS resolution | Nokia |
S3-252244 | Solution 19 figure update and formatting issues | Nokia |
S3-252245 | Solution 20 figure update and formatting issues | Nokia |
S3-252246 | Solution 21 restructuring and formatting | Nokia |
TDoc | Title | Source |
---|---|---|
S3-251860 | Cryptographic Inventory Table update for MIKEY-SAKKE | NIST |
S3-251874 | Tables Content for ECIES | Nokia, Nokia Shanghai Bell |
S3-251875 | Tables Content for PKI | Nokia, Nokia Shanghai Bell |
S3-251876 | Tables Content for OCSP | Nokia, Nokia Shanghai Bell |
S3-251877 | Tables Content for COSE | Nokia, Nokia Shanghai Bell |
S3-251878 | Tables Content for KDF | Nokia, Nokia Shanghai Bell |
S3-251879 | Tables Content for EAP-TLS | Nokia, Nokia Shanghai Bell |
S3-251880 | Editorial Modifications | Nokia, Nokia Shanghai Bell |
S3-251881 | Terms and Definitions | Nokia, NIST |
S3-251882 | Coverpage for TR Cryptographic Inventory | Nokia, Nokia Shanghai Bell |
S3-251975 | missing references and abbreviations | Huawei, HiSilicon |
S3-251976 | descriptioin of EAP-TTLS | Huawei, HiSilicon |
S3-251977 | description of OAuth 2.0 | Huawei, HiSilicon |
S3-251978 | Table content for EAP-TTLS | Huawei, HiSilicon |
S3-251979 | Table content for OAuth 2.0 | Huawei, HiSilicon |
S3-251980 | Table content for IKEv2 | Huawei, HiSilicon |
S3-251981 | Table content for PDCP | Huawei, HiSilicon |
S3-251982 | Table content for NAS | Huawei, HiSilicon |
S3-252042 | pCR on Tables Content for IPsec ESP protocol | Samsung |
S3-252172 | Pseudo-CR on 3GPP Cryptographic Inventory Table for DTLS | Qualcomm Incorporated |
S3-252173 | Pseudo-CR on 3GPP Cryptographic Inventory Table for TLS | Qualcomm Incorporated |
S3-252174 | Pseudo-CR on 3GPP Cryptographic Inventory Table for JWE and JWS | Qualcomm Incorporated |
S3-252175 | Pseudo-CR on 3GPP Cryptographic Inventory Clause Restructuring | Qualcomm Incorporated |
S3-252176 | Pseudo-CR on 3GPP Cryptographic Inventory EAP-TLS Details | Qualcomm Incorporated |
S3-252177 | Pseudo-CR on 3GPP Cryptographic Inventory Abbreviations | Qualcomm Incorporated |
S3-252178 | Pseudo-CR on 3GPP Cryptographic Inventory OCSP Details | Qualcomm Incorporated |
S3-252179 | Pseudo-CR on 3GPP Cryptographic Inventory QUIC Details | Qualcomm Incorporated |
S3-252206 | 3GPP Cryptographic Inventory Table for EAP-AKA’/EAP-5G | Lenovo |
TDoc | Title | Source |
---|---|---|
S3-251829 | New WID on mission critical security enhancements for release 20 | Motorola Solutions Germany |
S3-251864 | Study on Transition of 3GPP Cryptographic Algorithms to PQC | Nokia, Nokia Shanghai Bell |
S3-251873 | Discussion on Transition to PQC | Nokia, Nokia Shanghai Bell |
S3-251983 | Discussion paper on PQC migration | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
S3-251912 | Summary of NWM discussion on R-20 planning | NTT DOCOMO INC. |
S3-251965 | New SID on Security aspects of WAB nodes for NR | Nokia, ZTE |
S3-252026 | Discussion Paper on 6G NWM process and questions | vivo |
S3-252102 | Discussion paper on SA3 R20 work plan | Apple |
S3-252186 | LGE View on 6G study | LG Electronics |
S3-252204 | Revised WID on security support for the Next Generation Real Time Communication services Phase 2 | Ericsson |
S3-252253 | 6G security SID discussion | NTT DOCOMO INC. |
TDoc | Title | Source |
---|---|---|
S3-251838 | Security related Events Handling | Vodafone, AT&T, BT, Charter Communications, Deutsche Telekom, Ericsson, IIT Bombay, KDDI, Nokia, NTT DOCOMO, Orange, Telecom Italia, Telefonica, T-Mobile USA, Verizon |
S3-251859 | Discussion on threats for CNF products and CNF SCAS Test Cases | BSI (DE), Montsecure |
S3-251891 | New SID on AIMLE Service Security | Lenovo, Motorola Mobility |
S3-251900 | Draft Technical Specification; Security related Events Handling | Pairpoint |
S3-251904 | Discussion on Security Aspects for IMS resiliency study | KDDI, Boost Mobile Network |
S3-251905 | New SID on Security Aspects for IMS resiliency | KDDI, AT&T, Boost Mobile Network, Deutsche Telekom, SK Telecom, SoftBank, TOYOTA MOTOR CORPORATION, Rakuten Mobile, Verizon, vivo, Vodafone |
S3-251910 | New WID on PRINS Refinement | CableLabs |
S3-251911 | New SID on Security Plane for collection and transport of security data | OTD_US |
S3-251928 | New Study on Indirect Communication Security | MITRE-FFRDC |
S3-251956 | New SID on Security Aspect for NR Femto Phase 2 | ZTE Corporation |
S3-251957 | discussion paper on the MAC layer security | ZTE Corporation |
S3-251958 | New SID on MAC layer security | ZTE Corporation |
S3-251967 | Discussion on Security Aspect for NR Femto Phase 2 | ZTE Corporation |
S3-251985 | Discussion paper on security for PLMN hosting a NPN phase 2 | China Telecommunications Corp.,ZTE |
S3-251986 | New SID on security for PLMN hosting a NPN phase 2 | China Telecommunications Corp.,ZTE, China Unicom, China Mobile |
S3-251987 | New SID on Security Aspects for Evolved Residential Gateways Accessing to 5G Core Network | China Unicom, Huawei, HiSilicon |
S3-251996 | new SID on security aspects for QUIC or TLS | Huawei, HiSilicon |
S3-251997 | Discussion paper on security aspects for QUIC or TLS | Huawei, HiSilicon |
S3-252005 | New SID on security aspect of Sensing | Huawei, HiSilicon |
S3-252006 | Discussion on security aspects of Sensing | Huawei, HiSilicon, Xiaomi |
S3-252012 | New WID on SCAS | Huawei, HiSilicon,Huawei, HiSilicon, BSI (DE), China Telecom, China Mobile, Keysight Technologies UK Ltd., Nokia, Nokia Shanghai Bell, China Unicom, CATT, CAICT |
S3-252027 | New SID on Security of AIML_Ph2 | vivo, CMCC |
S3-252065 | New SID on enhanced security management service about security policy provisioning | China Mobile, ZTE, CATT, Johns Hopkins University APL, CAICT, CableLabs, Nokia, China Unicom, China Telecom |
S3-252069 | New SID on security aspects of Integrated Sensing and Communication | Xiaomi, China Telecom, China Mobile, ZTE, Lenovo, CableLabs |
S3-252079 | Discussion on R20 5G-A CAPIF security enhencements | Xiaomi communications |
S3-252087 | New SID on 5G Security Assurance Specification (SCAS) for the Container-based Products | Ericsson, Nokia, Nokia Shanghai Bell, BSI |
S3-252133 | New SID on Security Aspects of 5G Satellite Access Phase 4 | CATT, China Unicom |
S3-252134 | New WID on Security Aspects of Proximity based Services in NPNs | China Telecom Corporation Ltd. |
S3-252154 | Study on Post-Quantum Cryptography in 3GPP profiles for cryptographic algorithms and security protocols | Ericsson |
S3-252191 | Discussion on threats for CNF products and CNF SCAS Test Cases | BSI (DE) |
S3-252235 | Discussion on work split SA3 and SA6 on user consent topic | Nokia |
S3-252236 | DP related to FS_5GSAT_Ph4_SEC concerning NAS counters handling in multi-satellite S&F operation | Sateliot, Novamint |
S3-252238 | Mini WID for Roaming and interconnect authorization aspects in indirect communication | Nokia |
TDoc | Title | Source |
---|---|---|
S3-251861 | New SID on Security Infrastructure Support for 6G Core Network | Johns Hopkins University APL |
S3-251862 | New Study on Security Infrastructure Support for 6G Core Network | Johns Hopkins University APL |
S3-251892 | New SID on Secure UE Identification and Network Access | Lenovo, Motorola Mobility |
S3-251893 | Discussion on Secure UE Identification and Network Access | Lenovo, Motorola Mobility |
S3-251961 | New SID on inter-PLMN and intra-PLMN security in 6G | China Mobile |
S3-251966 | Discussion paper on security of RRC initial access | Nokia |
S3-252013 | 6G Security SID process and scope discussion | Huawei, HiSilicon |
S3-252015 | New SID on supporting AEAD algorithms | KDDI Corporation |
S3-252016 | Discussion paper on supporting AEAD algorithms | KDDI Corporation |
S3-252028 | Discussion Paper on Potential 6G Independent Security Areas | vivo |
S3-252066 | New SID on supporting AEAD algorithms | KDDI Corporation |
S3-252135 | Security Consideration for Integrated Sensing and Communication | OPPO |
S3-252190 | Security consideration for MAC CE and lower layers | OPPO |
S3-252192 | Study on Security Aspects of Lower Layers | OPPO |
TDoc | Title | Source |
---|---|---|
S3-251814 | SA3 meeting calendar | SA WG3 Chair |
S3-251871 | Handling of ETSI-SAGE documents | Rapporteur of the 256-Algo WI, MCC |