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-243831 | Draft TR 33.743 | draft TR | Huawei | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] | |
| S3-243965 | Terminology alignment of TR 33.743 | pCR | Huawei, HiSilicon | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-243966 | Discussion on multi-hop U2NW relay solutions and way forward for the conclusion | discussion | Huawei, HiSilicon | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
noted | [WTS] [JSN] | |
| S3-243967 | Update the evaluation of solution 5 in TR 33.743 |
pCR revised to S3-244481 |
Huawei, HiSilicon | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243968 | Conclusion to KI#1 - multi-hop U2NW discovery |
pCR revised to S3-244375 |
Huawei, HiSilicon | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-243969 | Conclusion to KI#1 - multi-hop U2NW link setup | pCR | Huawei, HiSilicon | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-243970 | Conclusion to KI#2 - multi-hop U2U discovery | pCR | Huawei, HiSilicon | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-243971 | Conclusion to KI#2 - multi-hop U2U link setup | pCR | Huawei, HiSilicon | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-243972 | Reply LS on security considerations for 5G ProSew multi-hop relays |
LS out LS is reply to S3-243821 source LS: S2-2407207 LS To: SA2 |
Huawei, HiSilicon | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] | |
| S3-244020 | TR 33.743 Conclusion for Key Issue#1 |
pCR revised to S3-244376 |
InterDigital Communications | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244116 | Update to solution #7 in TR 33.743 |
pCR revised to S3-244513 |
Beijing Xiaomi Mobile Software | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244117 | Update to solution #8 in TR 33.743 |
pCR revised to S3-244372 |
Beijing Xiaomi Mobile Software | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244118 | Conclusion for KI#1 in TR 33.743 | pCR | Beijing Xiaomi Mobile Software | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-244119 | Reply LS on security considerations for 5G ProSe multi-hop relays |
LS out LS is reply to S3-243821 source LS: S2-2407207 LS To: SA2 |
Beijing Xiaomi Mobile Software | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] | |
| S3-244140 | reply LS on security considerations for 5G ProSe multi-hop relays |
LS out LS is reply to S3-243821 LS To: SA2 revised to S3-244371 |
Qualcomm Incorporated |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] | |||
| S3-244141 | A new solution for multi-hop U2N relay communication security |
pCR revised to S3-244498 |
Qualcomm Incorporated | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244142 | Conclusion of KI#1 | pCR | Qualcomm Incorporated | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-244143 | Conclusion of KI#2 |
pCR revised to S3-244377 |
Qualcomm Incorporated | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244144 | Updating evaluations to solution #9 |
pCR revised to S3-244374 |
Qualcomm Incorporated | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244145 | Updating evaluations to solution #7 | pCR | Qualcomm Incorporated | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-244197 | Update Solution#2 |
pCR revised to S3-244496 |
Ericsson | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244198 | Update Solution#3 |
pCR revised to S3-244497 |
Ericsson | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
revised | [WTS] [JSN] |
| S3-244199 | Update Solution#4 | pCR | Ericsson | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
noted | [WTS] [JSN] |
| S3-244218 | Conclusion of KI#1 | pCR | China Telecom Corporation Ltd. | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-244221 | Conclusion of KI#2 | pCR | China Telecom Corporation Ltd. | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-244222 | Reply LS on security considerations for 5G ProSe multi-hop relays |
LS out LS To: SA2 |
China Telecom Corporation Ltd. | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] | ||
| S3-244239 | pCR to TR33.743 Conclusion of KI#1 | pCR | CATT | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-244241 | pCR to TR33.743 Conclusion of KI#2 | pCR | CATT | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
merged | [WTS] [JSN] |
| S3-244371 | reply LS on security considerations for 5G ProSe multi-hop relays |
LS out LS is reply to S3-243821 LS To: SA2 revision of S3-244140 |
Qualcomm Incorporated |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] | |||
| S3-244372 | Update to solution #8 in TR 33.743 |
pCR revision of S3-244117 |
Beijing Xiaomi Mobile Software | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-244373 | Update Solution#4 | pCR | Ericsson | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
withdrawn | [WTS] [JSN] |
| S3-244374 | Updating evaluations to solution #9 |
pCR revision of S3-244144 |
Qualcomm Incorporated | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-244375 | Conclusion to KI#1 - multi-hop U2NW discovery |
pCR revision of S3-243968 |
Huawei, HiSilicon | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
noted | [WTS] [JSN] |
| S3-244376 | TR 33.743 Conclusion for Key Issue#1 |
pCR revision of S3-244020 |
InterDigital Communications | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
noted | [WTS] [JSN] |
| S3-244377 | Conclusion of KI#2 |
pCR revision of S3-244143 |
Qualcomm Incorporated | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-244481 | Update the evaluation of solution 5 in TR 33.743 |
pCR revision of S3-243967 |
Huawei, HiSilicon | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-244496 | Update Solution#2 |
pCR revision of S3-244197 |
Ericsson | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-244497 | Update Solution#3 |
pCR revision of S3-244198 |
Ericsson | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-244498 | A new solution for multi-hop U2N relay communication security |
pCR revision of S3-244141 |
Qualcomm Incorporated | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
| S3-244513 | Update to solution #7 in TR 33.743 |
pCR revision of S3-244116 |
Beijing Xiaomi Mobile Software | 33.743 0.3.0 | FS_5G_ProSe_Ph3_SEC | Rel-19 |
S3-118 AI: 5.12 |
approved | [WTS] [JSN] |
40 documents (0.40751099586487 seconds)