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-1906061 | IAB security aspects | discussion | Huawei, HiSilicon |
R2-106 AI: 11.1.2 |
noted | [WTS] [JSN] | |||
| R2-1906074 | Discussion on IAB NSA procedure and SRB transmission (option c) |
discussion revision of R2-1905036 |
Huawei, HiSilicon |
R2-106 AI: 11.1.2 |
noted | [WTS] [JSN] | |||
| R2-1906075 | Support of using SA IAB in NSA network (option b) |
discussion revision of R2-1904982 |
Huawei, HiSilicon |
R2-106 AI: 11.1.2 |
noted | [WTS] [JSN] | |||
| R2-1906077 | BAP header security | discussion | Huawei, HiSilicon |
R2-106 AI: 11.1.2 |
noted | [WTS] [JSN] | |||
| R2-1906350 | Multi-connectivity support in IAB | discussion | Intel Corporation | NR_IAB-Core |
R2-106 AI: 11.1.2 |
not treated | [WTS] [JSN] | ||
| R2-1906534 | Discussion on IAB multiple connectivity | discussion | ZTE Corporation, Sanechips |
R2-106 AI: 11.1.2 |
not treated | [WTS] [JSN] | |||
| R2-1906535 | Discussion on IAB UP Protocol Stack | discussion | ZTE Corporation, Sanechips |
R2-106 AI: 11.1.2 |
not treated | [WTS] [JSN] | |||
| R2-1906537 | IAB with NSA operation |
discussion revised to R2-1908109 |
KDDI Corporation, AT&T |
R2-106 AI: 11.1.2 |
revised | [WTS] [JSN] | |||
| R2-1906719 | Discussion on IAB security and proposal for LS to SA3 | discussion | Samsung Electronics GmbH |
R2-106 AI: 11.1.2 |
noted | [WTS] [JSN] | |||
| R2-1906720 | [DRAFT] LS to SA3 on IAB security |
LS out LS To: SA3 |
Samsung Electronics GmbH | NR_IAB | Rel-16 |
R2-106 AI: 11.1.2 |
not treated | [WTS] [JSN] | |
| R2-1906726 | Discussion on bearer limit imposed by use of IPv6 flow label and proposal for response LS to RAN3 | discussion | Samsung Electronics GmbH |
R2-106 AI: 11.1.2 |
noted | [WTS] [JSN] | |||
| R2-1906728 | [Draft] Reply LS to RAN3 on bearer limit with IPv6 flow label |
LS out LS is reply to R2-1905518 LS To: RAN3 revised to R2-1908154 |
Samsung Electronics GmbH | NR_IAB | Rel-16 |
R2-106 AI: 11.1.2 |
revised | [WTS] [JSN] | |
| R2-1906735 | BAP header protection for IAB |
discussion revision of R2-1904680 |
Samsung Research America | NR_IAB-Core |
R2-106 AI: 11.1.2 |
noted | [WTS] [JSN] | ||
| R2-1906968 | Support of traffic terminated at MT of IAB node |
discussion revision of R2-1903975 |
Huawei, HiSilicon | NR_IAB-Core | Rel-16 |
R2-106 AI: 11.1.2 |
not treated | [WTS] [JSN] | |
| R2-1906983 | Identifier of UE bearer for DL bearer mapping | discussion | Huawei, HiSilicon | NR_IAB-Core | Rel-16 |
R2-106 AI: 11.1.2 |
noted | [WTS] [JSN] | |
| R2-1906992 | Support for LTE deployment at IAB node sites | discussion | Ericsson | NR_IAB-Core | Rel-16 |
R2-106 AI: 11.1.2 |
not treated | [WTS] [JSN] | |
| R2-1906998 | User plane aspects of supporting NR-DC for IAB nodes | discussion | Ericsson | NR_IAB-Core | Rel-16 |
R2-106 AI: 11.1.2 |
noted | [WTS] [JSN] | |
| R2-1907006 | L2-Structure for IAB nodes | discussion | Ericsson | NR_IAB-Core | Rel-16 |
R2-106 AI: 11.1.2 |
not treated | [WTS] [JSN] | |
| R2-1907034 | IAB resource coordination and scheduling |
discussion revised to R2-1909895 |
Sony | NR_IAB-Core | Rel-16 |
R2-106 AI: 11.1.2 |
not treated | [WTS] [JSN] | |
| R2-1907058 | Discussion on out-of-order packets for IPSec | discussion | Nokia, Nokia Shanghai Bell | NR_IAB-Core | Rel-16 |
R2-106 AI: 11.1.2 |
noted | [WTS] [JSN] | |
| R2-1907059 | Draft LS on out-of-order packets for IPSec |
LS out LS To: SA3 |
Nokia, Nokia Shanghai Bell | NR_IAB-Core | Rel-16 |
R2-106 AI: 11.1.2 |
noted | [WTS] [JSN] | |
| R2-1907060 | Requirements for SRB mapping in IAB | discussion | Nokia, Nokia Shanghai Bell | NR_IAB-Core | Rel-16 |
R2-106 AI: 11.1.2 |
not treated | [WTS] [JSN] | |
| R2-1907191 | Discussion on bearer limit with IPv6 flow label | discussion | Nokia, Nokia Shanghai Bell | NR_IAB-Core | Rel-16 |
R2-106 AI: 11.1.2 |
noted | [WTS] [JSN] | |
| R2-1907371 | Regarding use of IPv6 flow labels for 1:1 mapping in IAB | discussion | AT&T, KDDI, Telstra, Verizon, Sprint |
R2-106 AI: 11.1.2 |
noted | [WTS] [JSN] | |||
| R2-1907956 | Consideration on RLC channel type for MT’s own traffic |
discussion revision of R2-1905070 |
LG Electronics Inc. | NR_IAB-Core | Rel-16 |
R2-106 AI: 11.1.2 |
not treated | [WTS] [JSN] | |
| R2-1908024 | Introduction of dual connection in IAB for backhaul link failure handling | discussion | Samsung R&D Institute UK |
R2-106 AI: 11.1.2 |
not treated | [WTS] [JSN] | |||
| R2-1908028 | EN-DC support in IAB | discussion | Samsung R&D Institute UK |
R2-106 AI: 11.1.2 |
noted | [WTS] [JSN] | |||
| R2-1908029 | Discussion on NR DC architecture for IAB operation | discussion | Samsung R&D Institute UK |
R2-106 AI: 11.1.2 |
noted | [WTS] [JSN] | |||
| R2-1908109 | IAB with NSA operation |
discussion revision of R2-1906537 |
KDDI Corporation |
R2-106 AI: 11.1.2 |
noted | [WTS] [JSN] | |||
| R2-1908154 | Reply LS to RAN3 on bearer limit with IPv6 flow label |
LS out LS is reply to R2-1905518 LS To: RAN3 revision of R2-1906728 |
RAN2 | NR_IAB | Rel-16 |
R2-106 AI: 11.1.2 |
approved | [WTS] [JSN] |
30 documents (0.39132618904114 seconds)