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-242853 | TR 33.743 update solution #1 |
pCR revised to S3-243663 |
InterDigital Canada | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243015 | Update EN in solution#13 |
pCR revised to S3-243711 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243019 | Evaluation of solution#13 |
pCR revised to S3-243712 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243041 | Conclusion of KI#1 | pCR | China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
withdrawn | [WTS] [JSN] |
| S3-243043 | Conclusion of KI#2 |
pCR revised to S3-243573 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243089 | Resolve EN and evaluate to Sol#11 for multi-hop U2U security establishment |
pCR revised to S3-243669 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243090 | Resolve ENs in solution#5 of TR 33.743 |
pCR revised to S3-243560 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243091 | Update solution#5 to add security establishment with more than one intermediate relays | pCR | Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243092 | Evaluates to solution#5 of TR 33.743 |
pCR revised to S3-243561 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243093 | Evaluates to solution#4 of TR 33.743 |
pCR revised to S3-243568 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243094 | Evaluates to solution#6 of TR 33.743 |
pCR revised to S3-243670 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243095 | Evaluates to solution#1 of TR 33.743 | pCR | Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-243182 | Resolve the EN in Key issue #1 | pCR | China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
noted | [WTS] [JSN] |
| S3-243183 | update solution #6 in TR 33.743 |
pCR revised to S3-243562 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243184 | Conclusion of KI#1 | pCR | China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
noted | [WTS] [JSN] |
| S3-243231 | pCR to TR33.743 Update clause 3.1 and clause 3.3 | pCR | CATT | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243248 | pCR to TR33.743 Update clause 4 to standardize the use of terminology | pCR | CATT | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243257 | Update to solution #7 in TR 33.743 |
pCR revised to S3-243569 |
Beijing Xiaomi Mobile Software | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243258 | Update to solution #8 in TR 33.743 |
pCR revised to S3-243563 |
Beijing Xiaomi Mobile Software | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243259 | Add the evaluation of solution #7 in TR 33.743 |
pCR revised to S3-243710 |
Beijing Xiaomi Mobile Software | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243260 | Add the evaluation of solution #8 in TR 33.743 |
pCR revised to S3-243564 |
Beijing Xiaomi Mobile Software | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243300 | Resolve ENs in Solution #2: Security of multi-hop UE-to-Network Relay discovery Model A |
pCR revised to S3-243706 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243301 | Resolve EN in Solution #3: Security of multi-hop UE-to-Network Relay discovery Model B |
pCR revised to S3-243572 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243302 | Resolve EN in Solution#4: Security of multi-hop UE-to-Network Relay communication |
pCR revised to S3-243565 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243303 | Evaluation of Solution #2: Security of multi-hop UE-to-Network Relay discovery Model A |
pCR revised to S3-243707 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243304 | Evaluation of Solution #3: Security of multi-hop UE-to-Network Relay discovery Model B |
pCR revised to S3-243708 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243305 | Evaluation of Solution#4: Security of multi-hop UE-to-Network Relay communication |
pCR revised to S3-243566 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243306 | Resolve EN in KI#1: Security for multi-hop UE-to-Network Relay | pCR | Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
noted | [WTS] [JSN] |
| S3-243332 | Updates on solution #9 | pCR | Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243333 | Addressing ENs in solution #9 |
pCR revised to S3-243570 |
Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243334 | Adding an evaluation to solution #9 |
pCR revised to S3-243571 |
Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243335 | Updates to solution #10 | pCR | Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243336 | Addressing ENs in solution #10 | pCR | Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243337 | Adding an evaluation to solution #10 |
pCR revised to S3-243709 |
Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243338 | Updates on solution #14 | pCR | Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243339 | Add an evaluation to solution #15 | pCR | Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243560 | Resolve ENs in solution#5 of TR 33.743 |
pCR revision of S3-243090 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243561 | Evaluates to solution#5 of TR 33.743 |
pCR revision of S3-243092 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243562 | update solution #6 in TR 33.743 |
pCR revision of S3-243183 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243563 | Update to solution #8 in TR 33.743 |
pCR revision of S3-243258 |
Beijing Xiaomi Mobile Software | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243564 | Add the evaluation of solution #8 in TR 33.743 |
pCR revision of S3-243260 |
Beijing Xiaomi Mobile Software | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243565 | Resolve EN in Solution#4: Security of multi-hop UE-to-Network Relay communication |
pCR revision of S3-243302 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243566 | Evaluation of Solution#4: Security of multi-hop UE-to-Network Relay communication |
pCR revision of S3-243305 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243567 | Draft TR 33.743 | draft TR | Huawei | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] | |
| S3-243568 | Evaluates to solution#4 of TR 33.743 |
pCR revision of S3-243093 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243569 | Update to solution #7 in TR 33.743 |
pCR revision of S3-243257 |
Beijing Xiaomi Mobile Software | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243570 | Addressing ENs in solution #9 |
pCR revision of S3-243333 |
Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243571 | Adding an evaluation to solution #9 |
pCR revision of S3-243334 |
Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243572 | Resolve EN in Solution #3: Security of multi-hop UE-to-Network Relay discovery Model B |
pCR revision of S3-243301 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243573 | Conclusion of KI#2 |
pCR revision of S3-243043 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
noted | [WTS] [JSN] |
| S3-243663 | TR 33.743 update solution #1 |
pCR revision of S3-242853 |
InterDigital Canada | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243669 | Resolve EN and evaluate to Sol#11 for multi-hop U2U security establishment |
pCR revision of S3-243089 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243670 | Evaluates to solution#6 of TR 33.743 |
pCR revision of S3-243094 |
Huawei, HiSilicon | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243706 | Resolve ENs in Solution #2: Security of multi-hop UE-to-Network Relay discovery Model A |
pCR revision of S3-243300 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243707 | Evaluation of Solution #2: Security of multi-hop UE-to-Network Relay discovery Model A |
pCR revision of S3-243303 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243708 | Evaluation of Solution #3: Security of multi-hop UE-to-Network Relay discovery Model B |
pCR revision of S3-243304 |
Ericsson | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243709 | Adding an evaluation to solution #10 |
pCR revision of S3-243337 |
Qualcomm Incorporated | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243710 | Add the evaluation of solution #7 in TR 33.743 |
pCR revision of S3-243259 |
Beijing Xiaomi Mobile Software | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243711 | Update EN in solution#13 |
pCR revision of S3-243015 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243712 | Evaluation of solution#13 |
pCR revision of S3-243019 revised to S3-243723 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243723 | Evaluation of solution#13 |
pCR revision of S3-243712 |
China Telecom Corporation Ltd. | 33.743 0.2.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-117 AI: 5.12 |
approved | [WTS] [JSN] |
61 documents (0.40541100502014 seconds)