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-1706350 | Assisted Information for State Transition from CONNECTED to INACTIVE | discussion | OPPO | NR_newRAT-Core |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | ||
| R2-1706400 | Open issues on state transition from INACTIVE to CONNECTED | discussion | CATT | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1706449 | Inactivity-based transition to a power efficient state | discussion | Samsung | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1706632 | Multiplexing NAS messages with MSG3 | discussion | Ericsson | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1706693 | Timer-Based Inactivation for NR | discussion | InterDigital | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1706723 | State transition between RRC CONNECTED and INACTIVE | discussion | Huawei, HiSilicon | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1706724 | Security of INACTIVE to CONNECTED state transition | discussion | Huawei, HiSilicon | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1706725 | State transition from INACTIVE to IDLE | discussion | Huawei, HiSilicon | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1706726 | UE behaviour upon leaving RRC_CONNECTED state | discussion | Huawei, HiSilicon | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1706806 | Security procedure from RRC_INACTIVE state in NR | discussion | Samsung India |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |||
| R2-1706878 | Consideration on the triggers of transiting UE from INACTIVE to IDLE |
discussion revised to R2-1707458 |
Beijing Xiaomi Mobile Software | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
revised | [WTS] [JSN] | ||
| R2-1706930 | Discussion on RRC State Transition between Connected and Inactive | discussion | ITRI | NR_newRAT-Core |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | ||
| R2-1706967 | UE AS context retrieve failure |
discussion revised to R2-1708419 |
vivo | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1707040 | Security optimizations when resuming or re-establishing | discussion | Intel Corporation | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1707041 | [DRAFT] LS on security when resuming or re-establishing | discussion | Intel Corporation | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1707084 | Discussion on UE release from INACTIVE to IDLE |
discussion revised to R2-1708368, R2-1711480 |
Guangdong OPPO Mobile Telecom. | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1707088 | Generic Access Barring | discussion | MediaTek Inc. |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |||
| R2-1707228 | Mechanism design to avoid unnecessary inter-gNB mobility upon state transitions in NR | discussion | ASTRI, TCL Communication Ltd. |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |||
| R2-1707233 | RRC Connection establishment procedures | discussion | Nokia | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1707240 | RRC connection release and inactivation procedures | discussion | Nokia | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1707298 | Addressing key FFS in email discussion [98#30][NR] RRC Connection Control | discussion | Ericsson | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1707303 | UE Context ID discussion | discussion | Ericsson | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1707341 | RAN2 consideration on control plane latency enhancement |
discussion revision of R2-1705248 |
Samsung Electronics Co., Ltd |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |||
| R2-1707362 | Information to include within RRC Activation and Inactivation | discussion | Samsung Electronics |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |||
| R2-1707435 | Draft LS to RAN1 on MSG3 size | discussion | Huawei, HiSilicon | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1707436 | Consideration on RRC connection establishment procedure | discussion | Huawei, HiSilicon | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1707441 | RRC support of Multiple numerologies | discussion | Huawei, HiSilicon | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1707446 | Draft LS to SA3 on inactive to connected state transition | discussion | Huawei, HiSilicon | NR_newRAT-Core | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] | |
| R2-1707458 | Consideration on the triggers of transiting UE from INACTIVE to IDLE |
discussion revision of R2-1706878 |
Beijing Xiaomi Mobile Software | Rel-15 |
R2-ah-18514 AI: 10.4.1.3.4 |
not treated | [WTS] [JSN] |
29 documents (0.39037108421326 seconds)