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-250001 | Agenda | agenda | SA WG3 Chair |
S3-119-e AI: 1 |
approved | [WTS] [JSN] | |||
| S3-250002 | Process for SA3#119AdHoc-e | other | SA WG3 Chair |
S3-119-e AI: 1 |
noted | [WTS] [JSN] | |||
| S3-250003 | Detailed agenda planning | other | SA WG3 Chair |
S3-119-e AI: 1 |
noted | [WTS] [JSN] | |||
| S3-250004 | LS on security aspects of Ambient IoT | LS in | S2-2411049 |
S3-119-e AI: 3.1 |
postponed | [WTS] [JSN] | |||
| S3-250005 | LS on RAN2 outcome of Ambient IoT study | LS in | R2-2411263 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250006 | Reply to LS on Further Clarification for Ambient IoT Security | LS in | S1-244920 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250007 | LS on A-IoT Conclusions in SA WG2 | LS in | S2-2413035 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250008 | Reply LS on terminology alignment between SA6 and SA3 | LS in | S6-245644 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250009 | Reply LS on clarifications on consent management | LS in | SP-241934 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |||
| S3-250010 | New KI: Reader Authorization for 5G Ambient IoT Services | pCR | InterDigital, Inc. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250011 | KI#3, Conclusions | pCR | Sony | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250012 | KI#5, Conclusions | pCR | Sony | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250013 | Conclusion to key issue#1 |
pCR revised to S3-250195 |
Lenovo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250014 | Conclusion to key issue#3 | pCR | Lenovo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250015 | Conclusion to key issue#4 | pCR | Lenovo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250016 | Conclusion to key issue#5 | pCR | Lenovo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250017 | KI#1.1-Further conclusions on ROF authentication |
pCR revised to S3-250182 |
Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250018 | KI#1.2-Further conclusions on authorization information | pCR | Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250019 | KI#1.3-Further conclusions on granularity | pCR | Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250020 | remove EN for KI#1.1 | pCR | Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250021 | remove EN for KI#1.2 | pCR | Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250022 | remove EN in clause 6.4 |
pCR revised to S3-250212 |
Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250023 | editorial corrections in clauses 6.2 and 6.10 |
pCR revised to S3-250216 |
Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250024 | Resolving ENs in sol#6 in TR 33.713 | pCR | ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250025 | Evaluation for solution 6 |
pCR revised to S3-250208 |
ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250026 | Update the KI#2 in TR 33.713 | pCR | ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250027 | Update the KI#3 in TR 33.713 | pCR | ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250028 | Update the scope in TR 33.713 |
pCR revised to S3-250209 |
ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250029 | Conclusion for KI#1 | pCR | ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250030 | Conclusion for KI#2 | pCR | ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250031 | Conclusion for KI#3 | pCR | ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250032 | Conclusion for KI#4 | pCR | ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250033 | Conclusion for KI#5 | pCR | ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250034 | Conclusion for KI#3 |
pCR revised to S3-250211 |
ZTE Corporation | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250035 | Update to the conclusion for KI#1.2 | pCR | ZTE Corporation | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250036 | Update to the conclusion for KI#2 | pCR | ZTE Corporation | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250037 | Updates to Solution#21 |
pCR revised to S3-250187 |
Lenovo | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250038 | Solution to address KI#6 |
pCR revised to S3-250191 |
Lenovo | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250039 | Conclusion for KI#2 | pCR | China Telecom | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250040 | Update sol#17 to resolve EN | pCR | China Telecom | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250041 | Conclusion on AIOT KI#3 |
pCR revised to S3-250224 |
OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250042 | Update AIOT KI#3 | pCR | OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250043 | Reply LS on security aspects of Ambient IoT |
LS out LS is reply to S3-250004/S2-2411049 LS To: SA2 |
OPPO | Rel-19 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250044 | addressing the editor's note in solution#4 |
pCR revised to S3-250203 |
Huawei, HiSilicon | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250045 | Discussion paper on the conclusion on key issue#5 | pCR | Huawei, HiSilicon | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250046 | conclusion on key issue#4 |
pCR revised to S3-250206 |
Huawei, HiSilicon, OPPO, China Unicom | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250047 | Generic conclusion on AIoT |
pCR revised to S3-250204 |
Huawei, HiSilicon | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250048 | Resolve various EN's for KI#1 | pCR | Huawei, HiSilicon | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
merged | [WTS] [JSN] |
| S3-250049 | Conclusion for KI#1 | pCR | Huawei, HiSilicon | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
merged | [WTS] [JSN] |
| S3-250050 | conclusion to KI#2 | pCR | Huawei, HiSilicon | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
merged | [WTS] [JSN] |
| S3-250051 | Update on Solution #6-Digital asset request validation | pCR | Huawei, HiSilicon | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
noted | [WTS] [JSN] |
| S3-250052 | Conclusion to KI#3 in TR 33.721 | pCR | Huawei, HiSilicon | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
merged | [WTS] [JSN] |
| S3-250053 | Conclusion on key issue #1.2 in TR 33.700-22 | pCR | China Telecom | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250054 | Adding evaluation for solution#3 | pCR | Apple | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250055 | Update solution#8 |
pCR revised to S3-250175 |
Apple | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250056 | Update solution#28 |
pCR revised to S3-250176 |
Apple | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250057 | Update solution#31 | pCR | Apple | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250058 | Conclusion on KI#5 AIoT Authentication |
pCR revised to S3-250226 |
OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250059 | pCR to TR33.713 Update solution#9 to remove EN |
pCR revised to S3-250231 |
CATT | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250060 | pCR to TR33.713 New solution AIoT command message security protection procedure | pCR | CATT | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250061 | pCR to TR33.713 Generic conclusion | pCR | CATT | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250062 | Proposal for a conclusion to KI#1 |
pCR revised to S3-250171 |
Nokia, Deutsche Telekom, BMWK, IIT Bombay | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
revised | [WTS] [JSN] |
| S3-250063 | Proposal for a conclusion to KI#2 |
pCR revised to S3-250172 |
Nokia, Deutsche Telekom, IIT Bombay | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
revised | [WTS] [JSN] |
| S3-250064 | TR cleanup |
pCR revised to S3-250173 |
Nokia | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
revised | [WTS] [JSN] |
| S3-250065 | Presentation of Report to TSG: TR 33.766, Version 1.0.0 | TS or TR cover | Nokia | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
endorsed | [WTS] [JSN] | |
| S3-250066 | Proposal for a conclusion | pCR | Nokia | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250067 | Proposal for a resolution to an EN concerning counter synchronisation | pCR | Nokia | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250068 | Proposal for a resolution of an EN concerning alignment with RAN specifications | pCR | Nokia | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250069 | Proposal for a resolution to an EN concerning device constrains |
pCR revised to S3-250174 |
Nokia | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250070 | Proposal for a resolution to an EN concerning key identification | pCR | Nokia | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250071 | LS reply to LS on security aspects of Ambient IoT |
LS out source LS: S3-244641 LS To: SA2 |
Nokia | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | |
| S3-250072 | pCR to TR33.713 Conclusion#3 | pCR | CATT | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250073 | pCR to TR33.713 Conclusion#4 | pCR | CATT | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250074 | pCR to TR33.713 Conclusion#5 | pCR | CATT | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250075 | Conclusion for KI#2 in TR 33.713 |
pCR revised to S3-250223 |
OPPO, Xiaomi | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250076 | pCR to TR33.713 Update solution#30 to remove EN | pCR | CATT | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250077 | Resolving ENs for AIoT Security Sol#37 |
pCR revised to S3-250225 |
Xidian, OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250078 | Resolving ENs in Solution #42 of TR 33.713 |
pCR revised to S3-250183 |
KPN N.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250079 | New Solution to KI#5 |
pCR revised to S3-250177 |
Ericsson | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250080 | New key issue for secure storage in AIoT devices | pCR | Ericsson, Thales | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250081 | New Key Issue on Amplification of resource exhaustion by exploiting AIoT paging messages | pCR | Ericsson | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250082 | New key issue for Authenticated and authorized access to devices in Ambient IoT via 3GPP core | pCR | Ericsson | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250083 | Pseudo-CR-General conclusion for the architecture of AIoT |
pCR revised to S3-250232 |
China mobile | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250084 | Pseudo-CR-System architecture and security assumptions for AIoT services |
pCR revised to S3-250233 |
China mobile | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250085 | Pseudo-CR on New solution on AIoT privacy | pCR | China mobile | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250086 | Update to solution#27 |
pCR revised to S3-250188 |
Samsung | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250087 | Updates to conclusion for key issue#2 |
pCR revised to S3-250189 |
Samsung | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250088 | [TR 33.721] Update to solution#6 |
pCR revised to S3-250190 |
Samsung | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250089 | Updates to solution#6 |
other revised to S3-250184 |
Samsung | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
revised | [WTS] [JSN] | |
| S3-250090 | Evaluation updates for solution#6 |
other revised to S3-250185 |
Samsung | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
revised | [WTS] [JSN] | |
| S3-250091 | Conclusion for Key issue#2 | other | Samsung | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
merged | [WTS] [JSN] | |
| S3-250092 | Resolving EN in solution #22 |
pCR revised to S3-250186 |
Samsung | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250093 | Evaluation update for solution#22 | pCR | Samsung | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250094 | Resolving EN in solution #38 | pCR | Samsung | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250095 | Evaluation to solution #38 | pCR | Samsung | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250096 | New solution for Authorization of API invoker on one UE accessing resources related to another UE |
pCR revised to S3-250198 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250097 | Resolving EN in key issue #1.2 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250098 | Resolving ENs and evaluation of solution #11 |
pCR revised to S3-250199 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250099 | Resolving ENs and evaluation of solution #22 |
pCR revised to S3-250200 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250100 | Resolving ENs and evaluation of solution #26 |
pCR revised to S3-250201 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250101 | Conclusion reformulation for key issue #1.2 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250102 | Further conclusion for key issue #1.1 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250103 | Further conclusion for key issue #1.2 |
pCR revised to S3-250196 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250104 | Further conclusion for key issue #1.3 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
withdrawn | [WTS] [JSN] |
| S3-250105 | Further conclusion for key issue #2 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250106 | Conclusion for key issue #3 |
pCR revised to S3-250197 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250107 | Conclusion for key issue #4 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250108 | Conclusion for key issue #5 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250109 | Conclusion for key issue #6 | pCR | Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250110 | Conclusion for KI#4 in TR 33.713 | pCR | Beijing Xiaomi Mobile Software | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250111 | Conclusion for KI#5 in TR 33.713 | pCR | Beijing Xiaomi Mobile Software | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250112 | 33.721: Evaluation of Solution 10 |
pCR revised to S3-250213 |
Xiaomi EV Technology | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250113 | 33.721: Update to Conclusion on Key Issue #2 |
pCR revised to S3-250214 |
Xiaomi EV Technology | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250114 | 33.721: Conclusion on Key Issue #4 |
pCR revised to S3-250215 |
Xiaomi EV Technology | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250115 | Draft CR on TS 33.122 | draftCR | Xiaomi communications | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] | |
| S3-250116 | TR 33.700-22KI#1.1 conclusion update | pCR | Xiaomi communications | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250117 | TR 33.700-22KI#1.2 conclusion update | pCR | Xiaomi communications | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250118 | TR 33.700-22KI#1.3 conclusion update | pCR | Xiaomi communications | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250119 | TR 33.700-22KI#2 conclusion update | pCR | Xiaomi communications | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250120 | Solution#1 update: Addressing ENs |
pCR revised to S3-250230 |
Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250121 | Solution#1 evaluation update |
pCR revised to S3-250229 |
Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250122 | KI#1 update: Addressing EN | pCR | Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250123 | KI#3 update: Addressing ENs |
pCR revised to S3-250228 |
Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250124 | KI#4 update: Addressing ENs |
pCR revised to S3-250227 |
Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250125 | KI#3 conclusions | pCR | Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250126 | KI#4 conclusions | pCR | Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250127 | KI#5 conclusions | pCR | Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250128 | Conclusion for KI#1 | pCR | Ericsson | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
merged | [WTS] [JSN] |
| S3-250129 | Conclusion for KI#2 | pCR | Ericsson | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
merged | [WTS] [JSN] |
| S3-250130 | LS on User Consent aspects for Energy Saving |
LS out LS To: SA WG2 |
Ericsson | Rel-19 |
S3-119-e AI: 3.1 |
noted | [WTS] [JSN] | ||
| S3-250131 | Solution#5 update for alignment with SA2 and addressing EN |
pCR revised to S3-250207 |
HUAWEI TECHNOLOGIES Co. Ltd. | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.2 |
revised | [WTS] [JSN] |
| S3-250132 | Conclusion to KI#2 of NG_RTC |
pCR revised to S3-250192 |
HUAWEI TECHNOLOGIES Co. Ltd. | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.2 |
revised | [WTS] [JSN] |
| S3-250133 | Conclusion to KI#3 of NG_RTC |
pCR revised to S3-250210 |
HUAWEI TECHNOLOGIES Co. Ltd. | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.2 |
revised | [WTS] [JSN] |
| S3-250134 | Update on Key Issue#6 |
pCR revised to S3-250217 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250135 | Sol#10 update |
pCR revised to S3-250218 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250136 | Sol#40 update |
pCR revised to S3-250219 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250137 | Sol#41 update |
pCR revised to S3-250220 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250138 | Conclusion for Key Issue#4 Information Protection | pCR | vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250139 | Conclusion for Key Issue#5 AIoT Authentication | pCR | vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250140 | Conclusion to KI#1 |
pCR revised to S3-250193 |
OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250141 | Solution#3 update | pCR | OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250142 | Solution#18 update | pCR | OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250143 | Solution#19 update | pCR | OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250144 | Authorization of external AF for Inventory |
pCR revision of S3-245132 revised to S3-250194 |
NTT DOCOMO INC. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
revised | [WTS] [JSN] |
| S3-250145 | KI on attacking via external carrier wave |
pCR revised to S3-250945 |
NTT DOCOMO INC. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250146 | Evaluation for Sol2 Authorization supporting spatial localization service with CCF | pCR | Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250147 | Update Sol3 Authorization supporting spatial localization service with CCF |
pCR revised to S3-250178 |
Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250148 | Update Sol5 Privacy protection during metaverse service discovery |
pCR revised to S3-250179 |
Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250149 | Update Sol7 authorize avatar by metaverse service provider | pCR | Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250150 | Update Sol8 authenticate and authorize DA client to create a digital asset |
pCR revised to S3-250180 |
Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250151 | Update Sol9 authenticate and authorize DA client to access a digital asset |
pCR revised to S3-250181 |
Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
revised | [WTS] [JSN] |
| S3-250152 | Conclusion for KI3 Security aspects of digital asset container in 5G | pCR | Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
merged | [WTS] [JSN] |
| S3-250153 | Conclusion for KI4 Authentication and authorization of digital representation | pCR | Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
merged | [WTS] [JSN] |
| S3-250154 | Conclusion for KI2 IMS based Avatar Communication | other | Nokia, Nokia Shanghai Bell | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
merged | [WTS] [JSN] | |
| S3-250155 | Update KI#1: Third party specific user identities to include NEF-AF interface security | other | Ericsson | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
noted | [WTS] [JSN] | |
| S3-250156 | LS on IMS support for AF authorization |
LS out LS To: SA2 revised to S3-250170 |
Ericsson | Rel-19 |
S3-119-e AI: 5.2 |
revised | [WTS] [JSN] | ||
| S3-250157 | Conclusion for KI3 IMS DC capability exposure | other | Nokia, Nokia Shanghai Bell | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
merged | [WTS] [JSN] | |
| S3-250158 | Comments on S3-250145, “KI on attacking via external carrier wave” | pCR | InterDigital, Inc. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250159 | Generic conclusion for AIoT | pCR | Qualcomm Incorporated | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
merged | [WTS] [JSN] |
| S3-250160 | KI1.1 ROF authentication conclusion | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250161 | KI1.1 ROF authentication | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250162 | KI1.1 Solution 3 update | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250163 | KI1.2 EN resolution in solution 7 | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250164 | KI1.3 conclusion |
pCR revised to S3-250222 |
Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] |
| S3-250165 | KI2 interconnect conclusion | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250166 | KI3 conclusion | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250167 | KI4 Nested API invocation conclusion | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250168 | KI5 muliple API infovoker same RO conclusion | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250169 | TR correction | pCR | Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
merged | [WTS] [JSN] |
| S3-250170 | LS on IMS support for AF authorization and IMS avatar communication |
LS out LS To: SA2 revision of S3-250156 |
Ericsson | Rel-19 |
S3-119-e AI: 5.2 |
approved | [WTS] [JSN] | ||
| S3-250171 | Proposal for a conclusion to KI#1 |
pCR revision of S3-250062 |
Nokia, Deutsche Telekom, BMWK, IIT Bombay, Ericsson, Huawei, HiSilicon | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-250172 | Proposal for a conclusion to KI#2 |
pCR revision of S3-250063 |
Nokia, Deutsche Telekom, IIT Bombay, Ericsson, Huawei, HiSilicon | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-250173 | TR cleanup |
pCR revision of S3-250064 |
Nokia, Huawei, HiSilicon | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
approved | [WTS] [JSN] |
| S3-250174 | Proposal for a resolution to an EN concerning device constrains |
pCR revision of S3-250069 |
Nokia | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250175 | Update solution#8 |
pCR revision of S3-250055 |
Apple | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250176 | Update solution#28 |
pCR revision of S3-250056 |
Apple | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250177 | New Solution to KI#5 |
pCR revision of S3-250079 |
Ericsson | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250178 | Update Sol3 Authorization supporting spatial localization service with CCF |
pCR revision of S3-250147 |
Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250179 | Update Sol5 Privacy protection during metaverse service discovery |
pCR revision of S3-250148 |
Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250180 | Update Sol8 authenticate and authorize DA client to create a digital asset |
pCR revision of S3-250150 |
Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250181 | Update Sol9 authenticate and authorize DA client to access a digital asset |
pCR revision of S3-250151 |
Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250182 | KI#1.1-Further conclusions on ROF authentication |
pCR revision of S3-250017 |
Huawei, HiSilicon, Ericsson, Xiaomi, Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250183 | Resolving ENs in Solution #42 of TR 33.713 |
pCR revision of S3-250078 |
KPN N.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250184 | Updates to solution#6 |
pCR revision of S3-250089 |
Samsung | 33.790 1.0.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-250185 | Evaluation updates for solution#6 |
pCR revision of S3-250090 |
Samsung | 33.790 1.0.0 | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-250186 | Resolving EN in solution #22 |
pCR revision of S3-250092 |
Samsung | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250187 | Updates to Solution#21 |
pCR revision of S3-250037 |
Lenovo | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250188 | Update to solution#27 |
pCR revision of S3-250086 |
Samsung | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250189 | Updates to conclusion for key issue#2 |
pCR revision of S3-250087 |
Samsung | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250190 | [TR 33.721] Update to solution#6 |
pCR revision of S3-250088 |
Samsung | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250191 | Solution to address KI#6 |
pCR revision of S3-250038 |
Lenovo | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250192 | Conclusion to KI#2 of NG_RTC |
pCR revision of S3-250132 |
HUAWEI TECHNOLOGIES Co. Ltd. | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-250193 | Conclusion to KI#1 |
pCR revision of S3-250140 |
OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250194 | Authorization of external AF for Inventory |
pCR revision of S3-250144 |
NTT DOCOMO INC. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250195 | Conclusion to key issue#1 |
pCR revision of S3-250013 |
Lenovo, ZTE, OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250196 | Further conclusion for key issue #1.2 |
pCR revision of S3-250103 |
Ericsson, Huawei, HiSilicon, ZTE Corporation, China Telecom, Xiaomi communications, Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250197 | Conclusion for key issue #3 |
pCR revision of S3-250106 |
Ericsson, Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250198 | New solution for Authorization of API invoker on one UE accessing resources related to another UE |
pCR revision of S3-250096 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250199 | Resolving ENs and evaluation of solution #11 |
pCR revision of S3-250098 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250200 | Resolving ENs and evaluation of solution #22 |
pCR revision of S3-250099 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250201 | Resolving ENs and evaluation of solution #26 |
pCR revision of S3-250100 |
Ericsson | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250202 | draft TR 33.713 v0.6.0 | draft TR | OPPO | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] | |
| S3-250203 | addressing the editor's note in solution#4 |
pCR revision of S3-250044 |
Huawei, HiSilicon | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250204 | Generic conclusion on AIoT |
pCR revision of S3-250047 |
Huawei, HiSilicon | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250205 | Draft TR 33.790 v1.1.0 Study on the security support for the next generation real time communication services phase 2 | draft TR | Ericsson Hungary Ltd | FS_NG_RTC_SEC_Ph2 | Rel-19 |
S3-119-e AI: 5.2 |
approved | [WTS] [JSN] | |
| S3-250206 | conclusion on key issue#4 |
pCR revision of S3-250046 |
Huawei, HiSilicon, OPPO, China Unicom, Lenovo, ZTE, CATT, Xiaomi, Philips | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250207 | Solution#5 update for alignment with SA2 and addressing EN |
pCR revision of S3-250131 |
HUAWEI TECHNOLOGIES Co. Ltd. | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-250208 | Evaluation for solution 6 |
pCR revision of S3-250025 |
ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250209 | Update the scope in TR 33.713 |
pCR revision of S3-250028 |
ZTE Corporation | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250210 | Conclusion to KI#3 of NG_RTC |
pCR revision of S3-250133 |
HUAWEI TECHNOLOGIES Co. Ltd. | 33.766 0.5.0 | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.2 |
approved | [WTS] [JSN] |
| S3-250211 | Conclusion for KI#3 |
pCR revision of S3-250034 |
ZTE Corporation | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250212 | remove EN in clause 6.4 |
pCR revision of S3-250022 |
Huawei, HiSilicon | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250213 | 33.721: Evaluation of Solution 10 |
pCR revision of S3-250112 |
Xiaomi EV Technology | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250214 | 33.721: Update to Conclusion on Key Issue #2 |
pCR revision of S3-250113 |
Xiaomi EV Technology | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250215 | 33.721: Conclusion on Key Issue #4 |
pCR revision of S3-250114 |
Xiaomi EV Technology, Nokia, Nokia Shanghai Bell | 33.721 0.5.0 | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] |
| S3-250216 | editorial corrections in clauses 6.2 and 6.10 |
pCR revision of S3-250023 |
Huawei, HiSilicon, Nokia | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] |
| S3-250217 | Update on Key Issue#6 |
pCR revision of S3-250134 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250218 | Sol#10 update |
pCR revision of S3-250135 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250219 | Sol#40 update |
pCR revision of S3-250136 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250220 | Sol#41 update |
pCR revision of S3-250137 |
vivo | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250221 | Draft TR 33.766 v0.6.0 | draft TR | Ericsson | FS_Energy_Sec | Rel-19 |
S3-119-e AI: 5.16 |
approved | [WTS] [JSN] | |
| S3-250222 | KI1.3 conclusion |
pCR revision of S3-250164 |
Nokia, Huawei, HiSilicon, Xiaomi | 33.700-22 0.3.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
noted | [WTS] [JSN] |
| S3-250223 | Conclusion for KI#2 in TR 33.713 |
pCR revision of S3-250075 |
OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250224 | Conclusion on AIOT KI#3 |
pCR revision of S3-250041 |
OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
noted | [WTS] [JSN] |
| S3-250225 | Resolving ENs for AIoT Security Sol#37 |
pCR revision of S3-250077 |
Xidian, OPPO | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250226 | Conclusion on KI#5 AIoT Authentication |
pCR revision of S3-250058 |
OPPO, Huawei, HiSilicon, Apple | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250227 | KI#4 update: Addressing ENs |
pCR revision of S3-250124 |
Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250228 | KI#3 update: Addressing ENs |
pCR revision of S3-250123 |
Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250229 | Solution#1 evaluation update |
pCR revision of S3-250121 |
Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250230 | Solution#1 update: Addressing ENs |
pCR revision of S3-250120 |
Philips International B.V. | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250231 | pCR to TR33.713 Update solution#9 to remove EN |
pCR revision of S3-250059 |
CATT | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250232 | Pseudo-CR-General conclusion for the architecture of AIoT |
pCR revision of S3-250083 |
China mobile | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250233 | Pseudo-CR-System architecture and security assumptions for AIoT services |
pCR revision of S3-250084 |
China mobile | 33.713 0.5.0 | FS_Ambient_IoT_Sec | Rel-19 |
S3-119-e AI: 5.9 |
approved | [WTS] [JSN] |
| S3-250234 | Draft TR 33.721 v0.6.0 | draft TR | Samsung | FS_Metaverse_Sec | Rel-19 |
S3-119-e AI: 5.18 |
approved | [WTS] [JSN] | |
| S3-250235 | Study on security aspects of CAPIF Phase3 |
draft TR revised to S3-250236 |
Ericsson LM | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
revised | [WTS] [JSN] | |
| S3-250236 | Study on security aspects of CAPIF Phase3 |
draft TR revision of S3-250235 |
Ericsson LM | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119-e AI: 5.19 |
approved | [WTS] [JSN] | |
| S3-250237 | SA3 Leadership meeting notes | report | MCC |
S3-119-e AI: 3.1 |
available | [WTS] [JSN] |
237 documents (1.209822177887 seconds)