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-2202145 | Reply LS on LTE User Plane Integrity Protection (R3-221473; contact: Vodafone) |
LS in LS is reply to S3-214462 source LS: R3-221473 LS To: SA3, SA2 |
RAN3 | UPIP_SEC_LTE | Rel-17 |
R2-117-e AI: 9.4 |
noted | [WTS] [JSN] | |
| R2-2202717 | Introducing support of UP IP for EPC connected architectures using NR PDCP |
CR revised to R2-2203819 |
Huawei, HiSilicon, Vodafone, Ericsson | 36.331 16.7.0 CR#4763 catB | UPIP_SEC_LTE | Rel-17 |
R2-117-e AI: 9.4 |
revised | [WTS] [JSN] |
| R2-2202718 | Introducing support of UP IP for EPC connected architectures using NR PDCP |
CR revised to R2-2203820 |
Huawei, HiSilicon, Vodafone, Ericsson | 38.331 16.7.0 CR#2904 catB | UPIP_SEC_LTE | Rel-17 |
R2-117-e AI: 9.4 |
revised | [WTS] [JSN] |
| R2-2202719 | Introducing support of UP IP for EPC connected architectures using NR PDCP |
CR revised to R2-2203821 |
Huawei, HiSilicon, Vodafone, Ericsson | 36.3 16.7.0 CR#1353 catB | UPIP_SEC_LTE | Rel-17 |
R2-117-e AI: 9.4 |
revised | [WTS] [JSN] |
| R2-2202720 | Introducing support of UP IP for EPC connected architectures using NR PDCP |
CR revised to R2-2203822 |
Huawei, HiSilicon, Vodafone, Ericsson | 37.34 16.8.0 CR#294 catB | UPIP_SEC_LTE | Rel-17 |
R2-117-e AI: 9.4 |
revised | [WTS] [JSN] |
| R2-2202721 | Introducing support of UP IP for EPC connected architectures using NR PDCP |
CR revised to R2-2203823 |
Huawei, HiSilicon, Vodafone, Ericsson | 38.323 16.6.0 CR#85 catB | UPIP_SEC_LTE | Rel-17 |
R2-117-e AI: 9.4 |
revised | [WTS] [JSN] |
| R2-2202722 | Discussion on LTE User Plane Integrity Protection (SA3 LS) | discussion | Huawei, HiSilicon | UPIP_SEC_LTE | Rel-17 |
R2-117-e AI: 9.4 |
available | [WTS] [JSN] | |
| R2-2203369 | draft Reply LS on LTE User Plane Integrity Protection |
LS out LS is reply to S3-214462/R2-2200153 source LS: S3-214462/R2-2200153 LS To: SA3 |
Vodafone | Rel-17 |
R2-117-e AI: 9.4 |
available | [WTS] [JSN] | ||
| R2-2203632 | Updated Report of [AT117-e][203][UPIP] LTE UPIP configuration and capabilities (Vodafone) | discussion | Vodafone | UPIP_SEC_LTE-RAN-Core | Rel-17 |
R2-117-e AI: 9.4 |
revised | [WTS] [JSN] | |
| R2-2203663 | Reply LS on LTE User Plane Integrity Protection |
LS out LS is reply to R2-2200153/S3-214462 LS To: SA3 |
RAN2 | UPIP_SEC_LTE-RAN-Core | Rel-17 |
R2-117-e AI: 9.4 |
approved | [WTS] [JSN] | |
| R2-2203728 | Reply LS on LTE User Plane Integrity Protection (S2-2201518; contact: Huawei) |
LS in source LS: S2-2201518 LS To: RAN3, SA3 |
SA2 | UPIP_SEC_LTE | Rel-17 |
R2-117-e AI: 9.4 |
noted | [WTS] [JSN] | |
| R2-2203755 | Reply LS on LTE User Plane Integrity Protection (S3-220464; contact: Ericsson) |
LS in LS is reply to R3-221473 source LS: S3-220464 LS To: RAN3, SA2 |
SA3 | UPIP_SEC_LTE | Rel-17 |
R2-117-e AI: 9.4 |
noted | [WTS] [JSN] | |
| R2-2203765 | Report of second phase [AT117-e][203][UPIP] LTE UPIP configuration and capabilities (Vodafone) | discussion | Vodafone | UPIP_SEC_LTE-RAN-Core | Rel-17 |
R2-117-e AI: 9.4 |
noted | [WTS] [JSN] | |
| R2-2203819 | Introducing support of UP IP for EPC connected architectures using NR PDCP |
CR revision of R2-2202717 |
Huawei, HiSilicon, Vodafone, Ericsson, Qualcomm, Intel | 36.331 16.7.0 CR#47631 catB | UPIP_SEC_LTE-RAN-Core | Rel-17 |
R2-117-e AI: 9.4 |
agreed | [WTS] [JSN] |
| R2-2203820 | Introducing support of UP IP for EPC connected architectures using NR PDCP |
CR revision of R2-2202718 |
Huawei, HiSilicon, Vodafone, Ericsson, Qualcomm, Intel | 38.331 16.7.0 CR#29041 catB | UPIP_SEC_LTE-RAN-Core | Rel-17 |
R2-117-e AI: 9.4 |
agreed | [WTS] [JSN] |
| R2-2203821 | Introducing support of UP IP for EPC connected architectures using NR PDCP |
CR revision of R2-2202719 |
Huawei, HiSilicon, Vodafone, Ericsson, Qualcomm, Intel | 36.3 16.7.0 CR#13531 catB | UPIP_SEC_LTE-RAN-Core | Rel-17 |
R2-117-e AI: 9.4 |
agreed | [WTS] [JSN] |
| R2-2203822 | Introducing support of UP IP for EPC connected architectures using NR PDCP |
CR revision of R2-2202720 |
Huawei, HiSilicon, Vodafone, Ericsson, Qualcomm, Intel | 37.34 16.8.0 CR#2941 catB | UPIP_SEC_LTE-RAN-Core | Rel-17 |
R2-117-e AI: 9.4 |
agreed | [WTS] [JSN] |
| R2-2203823 | Introducing support of UP IP for EPC connected architectures using NR PDCP |
CR revision of R2-2202721 |
Huawei, HiSilicon, Vodafone, Ericsson, Qualcomm, Intel | 38.323 16.6.0 CR#851 catB | UPIP_SEC_LTE-RAN-Core | Rel-17 |
R2-117-e AI: 9.4 |
agreed | [WTS] [JSN] |
| R2-2204080 | Reply LS on LTE User Plane Integrity Protection (S3-220464; contact: Ericsson) |
LS in LS is reply to R3-221473 source LS: S3-220464 LS To: RAN3, SA2 |
SA3 | UPIP_SEC_LTE | Rel-17 |
R2-117-e AI: 9.4 |
noted | [WTS] [JSN] | |
| R2-2204181 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC (R3-222610; contact: Qualcomm) |
LS in LS is reply to S3-213272 source LS: R3-222610 LS To: SA3 |
RAN3 | UPIP_SEC_LTE-RAN-Core | Rel-17 |
R2-117-e AI: 9.4 |
available | [WTS] [JSN] |
20 documents (0.31746196746826 seconds)