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-210027 | Reply LS on the re-keying procedure for NR SL |
LS in LS reply in S3-210738, S3-210738 |
R2-2010963 |
S3-102-e AI: 4.1 |
replied to | [WTS] [JSN] | |||
S3-210065 | Error code details - Resolving ed note in 13.2.2.6 |
CR revision of S3-201797 |
Nokia, Nokia Shanghai Bell | 33.501 15.11.0 CR#9021 catF | 5G_eSBA | Rel-15 |
S3-102-e AI: 4.1 |
withdrawn | [WTS] [JSN] |
S3-210066 | TS 33.536 - overall clean-up |
CR revised to S3-210705 |
LG Electronics Inc. | 33.536 16.2.0 CR#22 catD | eV2XARC | Rel-16 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-210074 | Error code details - Resolving ed note in 13.2.2.6 |
CR revision of S3-201797 revised to S3-210723 |
Nokia, Nokia Shanghai Bell | 33.501 16.5.0 CR#9022 catF | 5G_eSBA | Rel-16 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-210075 | Error code details - Resolving ed note in 13.2.2.6 |
CR revised to S3-210724 |
Nokia, Nokia Shanghai Bell | 33.501 17.0.0 CR#1019 catA | 5G_eSBA | Rel-17 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-210102 | Optional registration of NF Service Consumer to NRF | CR | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.501 15.11.0 CR#1024 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-210103 | Optional registration of NF Service Consumer to NRF | CR | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.501 16.5.0 CR#1025 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-210104 | Optional registration of NF Service Consumer to NRF | CR | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon | 33.501 17.0.0 CR#1026 catA | 5GS_Ph1-SEC | Rel-17 |
S3-102-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-210135 | Clarifications regarding Authentication procedure for V2X PC5 unicast link |
CR revised to S3-210804 |
Nokia, Nokia Shanghai Bell | 33.536 16.2.0 CR#23 catF | eV2XARC | Rel-16 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-210238 | Correction to the access token storage in NF service consumer | CR | Huawei, HiSilicon | 33.501 15.11.0 CR#1033 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-210239 | Correction to the access token storage in NF service consumer |
CR revised to S3-210735 |
Huawei, HiSilicon | 33.501 16.5.0 CR#1034 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-210240 | Correction to the access token storage in NF service consumer |
CR revised to S3-210736 |
Huawei, HiSilicon | 33.501 17.0.0 CR#1035 catA | 5GS_Ph1-SEC | Rel-17 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-210250 | Clarification on key derivation |
CR revised to S3-210737 |
Huawei, HiSilicon | 33.536 16.2.0 CR#24 catF | eV2XARC | Rel-16 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-210251 | Reply LS about the layer to provide security |
LS out LS To: RAN2, CT1 revised to S3-210738 |
Huawei, HiSilicon | Rel-16 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] | ||
S3-210339 | Typo correction in clause 6.9.9.4 | CR | Xidian University | 33.501 17.0.0 CR#1042 catA | 5GS_Ph1-SEC | Rel-17 |
S3-102-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-210380 | Clarification on a figure and the key activation | CR | Huawei, HiSilicon | 33.535 16.2.0 CR#64 catF | eV2XARC | Rel-16 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-210382 | Align the JSON format on encryption IE with CT4 in Rel15 |
CR revised to S3-210748 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 15.11.0 CR#1046 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-210383 | Mirror: align the JSON format on encryption IE with CT4 in Rel16 |
CR revised to S3-210749 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 16.5.0 CR#1047 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-210384 | Mirror: align the JSON format on encryption IE with CT4 in Rel17 |
CR revised to S3-210750 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 17.0.0 CR#1048 catA | 5GS_Ph1-SEC | Rel-17 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-210385 | Adding the security requirement with encBlockIndex in Rel15 | CR | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 15.11.0 CR#1049 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-210386 | Mirror Adding the security requirement with encBlockIndex in Rel16 |
CR revised to S3-210751 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 16.5.0 CR#1050 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-210387 | Mirror Adding the security requirement with encBlockIndex in Rel17 |
CR revised to S3-210752 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 17.0.0 CR#1051 catA | 5GS_Ph1-SEC | Rel-17 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-210395 | Clarification on PLMN ID verification in Rel15 | CR | Huawei, HiSilicon | 33.501 15.11.0 CR#1052 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-210396 | Clarification on PLMN ID verification in Rel16 | CR | Huawei, HiSilicon | 33.501 16.5.0 CR#1053 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
not pursued | [WTS] [JSN] |
S3-210397 | Discussion paper on TAU reject issue during MME handover | discussion | Huawei, HiSilicon | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-210398 | LS on TAU reject issue during MME handover |
LS out LS To: CT4 |
Huawei, HiSilicon | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
noted | [WTS] [JSN] | |
S3-210413 | OAuth 2.0 client registration and NF Service registration | discussion | Ericsson |
S3-102-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-210467 | Typo correction in clause 6.9.9.4 | CR | Xidian University | 33.501 16.5.0 CR#1061 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
withdrawn | [WTS] [JSN] |
S3-210515 | Updated proposal to introduce draft-ietf-emu-rfc5448bis to TS 33.501 |
discussion revision of S3-203322 |
Ericsson |
S3-102-e AI: 4.1 |
noted | [WTS] [JSN] | |||
S3-210532 | Typo correction in clause 6.9.4.4 | CR | Xidian University | 33.501 15.11.0 CR#1064 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-210545 | resolving ed note on protection policy mismatch |
CR revised to S3-210792 |
NTT DOCOMO INC. | 33.501 15.11.0 CR#1065 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
revised | [WTS] [JSN] |
S3-210546 | Typo correction in clause 6.9.4.4 | CR | Xidian University | 33.501 16.5.0 CR#1066 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
withdrawn | [WTS] [JSN] |
S3-210547 | Typo correction in clause 6.9.4.4 | CR | Xidian University | 33.501 16.5.0 CR#1067 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
withdrawn | [WTS] [JSN] |
S3-210548 | Typo correction in clause 6.9.4.4 | CR | Xidian University | 33.501 16.5.0 CR#1068 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
withdrawn | [WTS] [JSN] |
S3-210549 | Typo correction in clause 6.9.4.4 | CR | Xidian University | 33.501 16.5.0 CR#1069 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
withdrawn | [WTS] [JSN] |
S3-210550 | Typo correction in clause 6.9.4.4 | CR | Xidian University | 33.501 16.5.0 CR#1070 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-210551 | resolving ed note on protection policy mismatch | CR | NTT DOCOMO INC. | 33.501 16.5.0 CR#1071 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
merged | [WTS] [JSN] |
S3-210552 | resolving ed note on protection policy mismatch | CR | NTT DOCOMO INC. | 33.501 17.0.0 CR#1072 catA | 5GS_Ph1-SEC | Rel-17 |
S3-102-e AI: 4.1 |
merged | [WTS] [JSN] |
S3-210705 | TS 33.536 - overall clean-up |
CR revision of S3-210066 |
LG Electronics Inc. | 33.536 16.2.0 CR#221 catF | eV2XARC | Rel-16 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-210723 | Resolving editor's note on encryption policy mismatch between SEPPs |
CR revision of S3-210074 |
NTT Docomo, Nokia, Nokia Shanghai Bell | 33.501 16.5.0 CR#9023 catA | 5GS_Ph1-SEC | Rel-16 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-210724 | Resolving editor's note on encryption policy mismatch between SEPPs |
CR revision of S3-210075 |
NTT Docomo, Nokia, Nokia Shanghai Bell | 33.501 17.0.0 CR#10191 catA | 5GS_Ph1-SEC | Rel-17 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-210735 | Correction to the access token storage in NF service consumer |
CR revision of S3-210239 |
Huawei, HiSilicon | 33.501 16.5.0 CR#10341 catF | TEI16 | Rel-16 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-210736 | Correction to the access token storage in NF service consumer |
CR revision of S3-210240 |
Huawei, HiSilicon | 33.501 17.0.0 CR#10351 catA | TEI16 | Rel-17 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-210737 | Clarification on key derivation |
CR revision of S3-210250 |
Huawei, HiSilicon | 33.536 16.2.0 CR#241 catF | eV2XARC | Rel-16 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-210738 | Reply LS about the layer to provide security |
LS out LS is reply to S3-210027 LS To: RAN2, CT1 revision of S3-210251 |
Huawei, HiSilicon | Rel-16 |
S3-102-e AI: 4.1 |
approved | [WTS] [JSN] | ||
S3-210748 | Align the JSON format on encryption IE with CT4 in Rel15 |
CR revision of S3-210382 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | 33.501 15.11.0 CR#10461 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-210792 | Resolving editor's note on encryption policy mismatch between SEPPs |
CR revision of S3-210545 |
NTT DOCOMO INC., Nokia, Nokia Shanghai Bell | 33.501 15.11.0 CR#10651 catF | 5GS_Ph1-SEC | Rel-15 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
S3-210804 | Clarifications regarding Authentication procedure for V2X PC5 unicast link |
CR revision of S3-210135 |
Nokia, Nokia Shanghai Bell | 33.536 16.2.0 CR#231 catF | eV2XARC | Rel-16 |
S3-102-e AI: 4.1 |
agreed | [WTS] [JSN] |
48 documents (0.29248785972595 seconds)