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 |
---|---|---|---|---|---|---|---|---|---|
R2-2102605 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC (C1-211461; contact: Qualcomm) |
LS in LS is reply to S3-210563 source LS: C1-211461 LS To: SA3 |
CT1 | UPIP_SEC | Rel-17 |
R2-113-bis-e AI: 9.3 |
noted | [WTS] [JSN] | |
R2-2102607 | User location identification from Carrier Aggregation secondary cell activation messages (FSAG Doc 88_009; contact: GSMA) |
LS in source LS: FSAG Doc 88_009 LS To: SA3, RAN2 |
GSMA |
R2-113-bis-e AI: 9.3 |
available | [WTS] [JSN] | |||
R2-2102659 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC (S2-2101306; contact: Qualcomm) |
LS in source LS: S2-2101306 LS To: SA3, CT1 |
SA2 | Rel-17 |
R2-113-bis-e AI: 9.3 |
noted | [WTS] [JSN] | ||
R2-2102667 | LS on User Plane Integrity Protection for eUTRA connected to EPC (S3-210563; contact: Vodafone) |
LS in source LS: S3-210563 LS To: RAN2, RAN3, CT4, SA2 LS reply in R2-2104335, R2-2104349 |
SA3 |
R2-113-bis-e AI: 9.3 |
noted | [WTS] [JSN] | |||
R2-2102703 | Introduction of event-based trigger for LTE MDT logging | draftCR | KDDI Corporation | TEI17 | Rel-17 |
R2-113-bis-e AI: 9.3 |
available | [WTS] [JSN] | |
R2-2102721 | Introduction of event-based trigger for LTE MDT logging | draftCR | KDDI Corporation | TEI17 | Rel-17 |
R2-113-bis-e AI: 9.3 |
available | [WTS] [JSN] | |
R2-2102819 | UE location attack based on SCell activation |
discussion revision of R2-2100483 |
Ericsson | Rel-17 |
R2-113-bis-e AI: 9.3 |
noted | [WTS] [JSN] | ||
R2-2103016 | User Plane Integrity Protection for eUTRA connected to EPC | discussion | Qualcomm Incorporated | UPIP_SEC | Rel-17 |
R2-113-bis-e AI: 9.3 |
available | [WTS] [JSN] | |
R2-2103295 | User Plane Integrity Protection for LTE | discussion | Samsung | Rel-17 |
R2-113-bis-e AI: 9.3 |
available | [WTS] [JSN] | ||
R2-2103865 | RAN impact on UP IP for eUTRA connected to EPC | discussion | Apple | Rel-17 |
R2-113-bis-e AI: 9.3 |
available | [WTS] [JSN] | ||
R2-2103928 | Discussion on Capturing PDCP Impacts for User Plane Integrity Protection |
discussion revision of R2-2101477 |
Ericsson |
R2-113-bis-e AI: 9.3 |
available | [WTS] [JSN] | |||
R2-2103962 | PDCP for Integrity protection for LTE EPC | discussion | Intel Corporation | Rel-17 |
R2-113-bis-e AI: 9.3 |
available | [WTS] [JSN] | ||
R2-2104039 | Discussion on user location identification from SCell Activation | discussion | Huawei, HiSilicon | Rel-17 |
R2-113-bis-e AI: 9.3 |
noted | [WTS] [JSN] | ||
R2-2104325 | Summary of [AT113bis-e][202][LTE] UPIP for LTE Rel-17 (Qualcomm) | discussion | Qualcomm | UPIP_SEC | Rel-17 |
R2-113-bis-e AI: 9.3 |
noted | [WTS] [JSN] | |
R2-2104335 | Draft Reply LS on User Plane Integrity Protection for eUTRA connected to EPC |
LS out LS is reply to R2-2102667 LS To: SA3, RAN3 revised to R2-2104349 |
Qualcomm Incorporated | UPIP_SEC | Rel-17 |
R2-113-bis-e AI: 9.3 |
revised | [WTS] [JSN] | |
R2-2104349 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC |
LS out LS is reply to R2-2102667 LS To: SA3, RAN3 revision of R2-2104335 |
RAN2 | UPIP_SEC | Rel-17 |
R2-113-bis-e AI: 9.3 |
approved | [WTS] [JSN] |
16 documents (0.32049989700317 seconds)