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-201522 | LS on the re-keying procedure for NR SL | LS in | R2-2005978 |
S3-100-e AI: 4.13 |
postponed | [WTS] [JSN] | |||
| S3-201548 | LS on technical reports on use cases and requirements as well as architecture for vehicular multimedia | LS in | ITU-T Focus Group on Vehicular Multimedia (FG-VM) |
S3-100-e AI: 4.13 |
noted | [WTS] [JSN] | |||
| S3-201557 | Clarification on the definition of KNRP-sess | CR | InterDigital, Inc., LG Electronics, Qualcomm Incorporated | 33.536 16.0.0 CR#1 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
agreed | [WTS] [JSN] |
| S3-201609 | Corrections on security establishment | CR | InterDigital, Inc. | 33.536 16.0.0 CR#2 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
not pursued | [WTS] [JSN] |
| S3-201689 | Clarification of handling of the user plane security policy in clause 5.3.3.1.4.2.3 | CR | ZTE Corporation | 33.536 16.0.0 CR#3 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
not pursued | [WTS] [JSN] |
| S3-201690 | Clean up for eV2X | CR | ZTE Corporation | 33.536 16.0.0 CR#4 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
merged | [WTS] [JSN] |
| S3-201691 | Update the clause 5.3.3.1.4.3 | CR | ZTE Corporation | 33.536 16.0.0 CR#5 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
not pursued | [WTS] [JSN] |
| S3-201692 | Update the clause 5.3.3.2.2 |
CR revised to S3-202232 |
ZTE Corporation | 33.536 16.0.0 CR#6 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
revised | [WTS] [JSN] |
| S3-201710 | Editorial changes about subscript corrections |
CR revised to S3-202212 |
Huawei, Hisilicon | 33.536 16.0.0 CR#7 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
revised | [WTS] [JSN] |
| S3-201711 | Propose to add descriptions about Knrp ID confliction | CR | Huawei, Hisilicon | 33.536 16.0.0 CR#8 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
not pursued | [WTS] [JSN] |
| S3-201712 | Clarification on policy handling |
CR revised to S3-202213 |
Huawei, Hisilicon | 33.536 16.0.0 CR#9 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
revised | [WTS] [JSN] |
| S3-201713 | Clarification on algorithm selection and key derivation |
CR revised to S3-202214 |
Huawei, Hisilicon | 33.536 16.0.0 CR#10 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
revised | [WTS] [JSN] |
| S3-201714 | Clarification on processing null-algorithms |
CR revised to S3-202215 |
Huawei, Hisilicon | 33.536 16.0.0 CR#11 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
revised | [WTS] [JSN] |
| S3-201715 | Propose to mitigate the bidding down attack | CR | Huawei, Hisilicon | 33.536 16.0.0 CR#12 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
not pursued | [WTS] [JSN] |
| S3-201716 | Propose to complete security lagorithm selection for UP |
CR revised to S3-202216 |
Huawei, Hisilicon | 33.536 16.0.0 CR#13 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
revised | [WTS] [JSN] |
| S3-201838 | Clarification on the UP security configuration checking |
CR revised to S3-202210 |
Huawei, Hisilicon | 33.536 16.0.0 CR#14 catB | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
revised | [WTS] [JSN] |
| S3-201839 | Clarification on the UP security policy activation | CR | Huawei, Hisilicon | 33.536 16.0.0 CR#15 catB | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
not pursued | [WTS] [JSN] |
| S3-201942 | Clarification on the unicast privacy procedures | CR | Qualcomm Incorporated | 33.536 16.0.0 CR#16 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
not pursued | [WTS] [JSN] |
| S3-202210 | Clarification on the UP security configuration checking |
CR revision of S3-201838 |
Huawei, Hisilicon | 33.536 16.0.0 CR#141 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
agreed | [WTS] [JSN] |
| S3-202212 | Editorial changes about eV2X |
CR revision of S3-201710 |
Huawei, Hisilicon, ZTE Corporation | 33.536 16.0.0 CR#71 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
agreed | [WTS] [JSN] |
| S3-202213 | Clarification on policy handling |
CR revision of S3-201712 |
Huawei, Hisilicon | 33.536 16.0.0 CR#91 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
agreed | [WTS] [JSN] |
| S3-202214 | Clarification on algorithm selection and key derivation |
CR revision of S3-201713 |
Huawei, Hisilicon | 33.536 16.0.0 CR#101 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
agreed | [WTS] [JSN] |
| S3-202215 | Clarification on processing null-algorithms |
CR revision of S3-201714 |
Huawei, Hisilicon | 33.536 16.0.0 CR#111 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
agreed | [WTS] [JSN] |
| S3-202216 | Propose to complete security lagorithm selection for UP |
CR revision of S3-201716 |
Huawei, Hisilicon | 33.536 16.0.0 CR#131 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
agreed | [WTS] [JSN] |
| S3-202232 | Update the clause 5.3.3.2.2 |
CR revision of S3-201692 |
ZTE Corporation | 33.536 16.0.0 CR#61 catF | eV2XARC | Rel-16 |
S3-100-e AI: 4.13 |
agreed | [WTS] [JSN] |
25 documents (0.28589510917664 seconds)