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-244616 | Updates to Solution #21 |
pCR revised to S3-245236 |
Lenovo | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244617 | Updates to Solution #5 |
pCR revised to S3-245221 |
Lenovo | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244747 | Evaluation to solution #4 in TR 33.700-22 | pCR | China Telecomunication Corp. | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-244772 | Evaluation for the Solution 23 |
pCR revised to S3-245237 |
ZTE Corporation | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244773 | Add evaluation to Sol#1 | pCR | ZTE Corporation | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244774 | Conclusion on KI#1.1 | pCR | ZTE Corporation | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244775 | Conclusion on KI#1.2 | pCR | ZTE Corporation | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244776 | Conclusion on KI#2 |
pCR revised to S3-245248 |
ZTE Corporation | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244778 | Evaluation to solution #5 in TR 33.700-22 | pCR | China Telecomunication Corp. | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
withdrawn | [WTS] [JSN] |
| S3-244779 | Update and evaluate solution #6 in TR 33.700-22 |
pCR revised to S3-245223 |
China Telecomunication Corp. | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244780 | Conclusion on key issue #1.2 in TR 33.700-22 | pCR | China Telecomunication Corp. | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244781 | Evaluation to solution #4 in TR 33.700-22 | pCR | China Telecomunication Corp. | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-244783 | Evaluation to solution #8 in TR 33.700-22 | pCR | China Telecomunication Corp. | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244784 | Evaluation to solution #9 in TR 33.700-22 | pCR | China Telecomunication Corp. | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244820 | Conclusion for KI#2 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244821 | Evaluation for sol#13 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244822 | Evaluation for sol#14 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244823 | Evaluation for sol#15 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244824 | Evaluation for sol#18 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244825 | Evaluation for sol#19 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244826 | Evaluation for sol#21 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244827 | Evaluation for sol#22 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244828 | Evaluation for sol#24 | pCR | China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244829 | Update sol#17 |
pCR revised to S3-245245 |
China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244832 | Solution 2 updates to address ENs | pCR | Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244833 | Adding evaluation to Solution 2 |
pCR revised to S3-245220 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244834 | Solution 4 updates to address ENs | pCR | Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-244835 | Adding evaluation to Solution 4 |
pCR revised to S3-245228 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244836 | Adding evaluation to Solution 10 |
pCR revised to S3-245233 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244837 | Conclusion to KI#1.1 |
pCR revised to S3-245222 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244838 | Conclusion to KI#1.2 |
pCR revised to S3-245231 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244839 | Conclusion to KI#1.3 |
pCR revised to S3-245235 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244870 | Conclusion for KI#3 | pCR | China Telecomunication Corp. | 33.700-32 0.4.0 | FS_UIA_Sec | Rel-19 |
S3-119 AI: 5.19 |
withdrawn | [WTS] [JSN] |
| S3-244928 | Addressing ENs on KI1.2 RO permission management in solution 7 |
pCR revised to S3-245226 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244929 | Update to KI1.3 Solution 29 on scope enhancing |
pCR revised to S3-245234 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244930 | Update to KI2 Solution 12 on security method retrieval in CAPIF interconnect |
pCR revised to S3-245246 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244931 | Update to KI2 Solution 13 on authentication aspect in CAPIF interconnect requesting security information from another CCF |
pCR revised to S3-245238 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244932 | Update to KI2 Solution 14 on authentication aspect in CAPIF interconnect when API invoker has not included CCF information |
pCR revised to S3-245239 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244933 | Update to KI2 Solution 15 on authorization token request handling in CAPIF interconnect |
pCR revised to S3-245240 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244934 | Update to KI2 Solution 16 on mapping an API invoker authorization request to the correct CCF in CAPIF interconnect |
pCR revised to S3-245247 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244935 | Update to KI5 Solution on authenticating multiple API invokers of the same RO |
pCR revised to S3-245254 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244937 | KI4 Sol on Authentication of the origin API invoker in nested API invocation |
pCR revised to S3-245250 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244938 | New KI on Onboarding security issue |
pCR revised to S3-245255 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244939 | Solution on validation of correct GPSI in API invoker information |
pCR revised to S3-245371 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-244940 | Correction of implementation mistake | pCR | Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-244941 | Update of mapping table | pCR | Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245030 | [TR 33.700-22] Update to solution#24 |
pCR revised to S3-245244 |
Samsung | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245031 | [TR 33.700-22] Update to solution#27 |
pCR revised to S3-245251 |
Samsung | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245032 | [TR 33.700-22] Conclusion for Key issue#4 | pCR | Samsung | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-245057 | Update to KI#1.2 |
pCR revised to S3-245232 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245058 | Resolving ENs and evaluation of Solution #11 |
pCR revised to S3-245227 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245059 | Resolving ENs and evaluation of Solution #22 |
pCR revised to S3-245243 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245060 | Update to Solution #25 and evaluation |
pCR revised to S3-245249 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245061 | Resolving EN and evaluation of Solution #26 |
pCR revised to S3-245252 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245109 | Add evaluation for solution #8 of TR 33.700-22 |
pCR revised to S3-245229 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245110 | Add evaluation for solution #9 of TR 33.700-22 |
pCR revised to S3-245224 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245111 | Add evaluation for solution #18 of TR 33.700-22 |
pCR revised to S3-245241 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245112 | Add evaluation for solution #19 of TR 33.700-22 |
pCR revised to S3-245242 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245113 | Add evaluation for solution #20 of TR 33.700-22 | pCR | Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245114 | Authorization mechanism for nested API invocation |
pCR revised to S3-245253 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245115 | Resolve ENs for solution #8 of TR 33.700-22 |
pCR revised to S3-245230 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245116 | Resolve ENs for solution #9 of TR 33.700-22 |
pCR revised to S3-245225 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
revised | [WTS] [JSN] |
| S3-245117 | Conclusion for CAPIF 6 and CAPIF 6e security | pCR | Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
merged | [WTS] [JSN] |
| S3-245118 | New WID on security aspects of CAPIF Phase3 | pCR | Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
withdrawn | [WTS] [JSN] |
| S3-245205 | Draft TR 33.700-22 | draft TR | Ericsson | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] | |
| S3-245220 | Adding evaluation to Solution 2 |
pCR revision of S3-244833 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245221 | Updates to Solution #5 |
pCR revision of S3-244617 |
Lenovo | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245222 | Conclusion to KI#1.1 |
pCR revision of S3-244837 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245223 | Update and evaluate solution #6 in TR 33.700-22 |
pCR revision of S3-244779 |
China Telecomunication Corp. | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245224 | Add evaluation for solution #9 of TR 33.700-22 |
pCR revision of S3-245110 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245225 | Resolve ENs for solution #9 of TR 33.700-22 |
pCR revision of S3-245116 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245226 | Addressing ENs on KI1.2 RO permission management in solution 7 |
pCR revision of S3-244928 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245227 | Resolving ENs and evaluation of Solution #11 |
pCR revision of S3-245058 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245228 | Adding evaluation to Solution 4 |
pCR revision of S3-244835 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245229 | Add evaluation for solution #8 of TR 33.700-22 |
pCR revision of S3-245109 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245230 | Resolve ENs for solution #8 of TR 33.700-22 |
pCR revision of S3-245115 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245231 | Conclusion to KI#1.2 |
pCR revision of S3-244838 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245232 | Update to KI#1.2 |
pCR revision of S3-245057 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
noted | [WTS] [JSN] |
| S3-245233 | Adding evaluation to Solution 10 |
pCR revision of S3-244836 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245234 | Update to KI1.3 Solution 29 on scope enhancing |
pCR revision of S3-244929 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245235 | Conclusion to KI#1.3 |
pCR revision of S3-244839 |
Huawei, HiSilicon | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245236 | Updates to Solution #21 |
pCR revision of S3-244616 |
Lenovo | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245237 | Evaluation for the Solution 23 |
pCR revision of S3-244772 |
ZTE Corporation | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245238 | Update to KI2 Solution 13 on authentication aspect in CAPIF interconnect requesting security information from another CCF |
pCR revision of S3-244931 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245239 | Update to KI2 Solution 14 on authentication aspect in CAPIF interconnect when API invoker has not included CCF information |
pCR revision of S3-244932 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245240 | Update to KI2 Solution 15 on authorization token request handling in CAPIF interconnect |
pCR revision of S3-244933 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245241 | Add evaluation for solution #18 of TR 33.700-22 |
pCR revision of S3-245111 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245242 | Add evaluation for solution #19 of TR 33.700-22 |
pCR revision of S3-245112 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245243 | Resolving ENs and evaluation of Solution #22 |
pCR revision of S3-245059 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245244 | [TR 33.700-22] Update to solution#24 |
pCR revision of S3-245030 |
Samsung | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245245 | Update sol#17 |
pCR revision of S3-244829 |
China Telecom | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245246 | Update to KI2 Solution 12 on security method retrieval in CAPIF interconnect |
pCR revision of S3-244930 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245247 | Update to KI2 Solution 16 on mapping an API invoker authorization request to the correct CCF in CAPIF interconnect |
pCR revision of S3-244934 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245248 | Conclusion on KI#2 |
pCR revision of S3-244776 |
ZTE Corporation | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245249 | Update to Solution #25 and evaluation |
pCR revision of S3-245060 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245250 | KI4 Sol on Authentication of the origin API invoker in nested API invocation |
pCR revision of S3-244937 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245251 | [TR 33.700-22] Update to solution#27 |
pCR revision of S3-245031 |
Samsung | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245252 | Resolving EN and evaluation of Solution #26 |
pCR revision of S3-245061 |
Ericsson | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245253 | Authorization mechanism for nested API invocation |
pCR revision of S3-245114 |
Xiaomi communications | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245254 | Update to KI5 Solution on authenticating multiple API invokers of the same RO |
pCR revision of S3-244935 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245255 | New KI on Onboarding security issue |
pCR revision of S3-244938 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [WTS] [JSN] |
| S3-245371 | Solution on validation of correct GPSI in API invoker information |
pCR revision of S3-244939 |
Nokia | 33.700-22 0.2.0 | FS_CAPIF_Ph3-sec | Rel-19 |
S3-119 AI: 5.19 |
approved | [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-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-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-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-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-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-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-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-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-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-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-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-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-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-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] |
163 documents (0.40393304824829 seconds)