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-2109601 | Discussion on two-level PERs for survival time handling | discussion | Huawei, HiSilicon | NR_IIOT_URLLC_enh-Core | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |
| R2-2109602 | Summary of [Post115-e][513][IIoT] QoS survival time | discussion | Huawei, HiSilicon | NR_IIOT_URLLC_enh-Core | Rel-17 |
R2-116-e AI: 8.5.4 |
noted | [WTS] [JSN] | |
| R2-2109603 | TP of baseline CR for Survival Time state operation | discussion | Huawei, HiSilicon | NR_IIOT_URLLC_enh-Core | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |
| R2-2109654 | HARQ NACK solution: addressing concerns and design details | discussion | CATT, CMCC | NR_IIOT_URLLC_enh-Core |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | ||
| R2-2109655 | TPs capturing HARQ-NACK solution | discussion | CATT | NR_IIOT_URLLC_enh-Core |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | ||
| R2-2109709 | L1/L2 configuration adaptation |
discussion revision of R2-2107658 revised to R2-2200311 |
Fujitsu | NR_IIOT_URLLC_enh-Core | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |
| R2-2109710 | Additional thought on supporting N>1 |
discussion revised to R2-2200309 |
Fujitsu | NR_IIOT_URLLC_enh-Core | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |
| R2-2109778 | RAN enhancements based on new QoS related parameters | discussion | Ericsson |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |||
| R2-2109927 | RAN Enhancement to support Survival Time | discussion | Qualcomm Incorporated | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | ||
| R2-2109992 | Discussion on HARQ NACK solution | discussion | vivo | NR_IIOT_URLLC_enh-Core | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |
| R2-2110067 | Remaining QoS solution aspects | discussion | Apple | NR_IIOT_URLLC_enh-Core | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |
| R2-2110068 | Adaptive configuration for CG/SPS | discussion | Apple | NR_IIOT_URLLC_enh-Core | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |
| R2-2110069 | Further considerations on survival time for new QoS | discussion | Apple | NR_IIOT_URLLC_enh-Core | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |
| R2-2110108 | N and combined Tx-side timer for IIoT QoS |
discussion revised to R2-2200704 |
ZTE, Sanechips, China Southern Power Grid Co., Ltd, TCL Communication Ltd., vivo | NR_IIOT_URLLC_enh-Core |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | ||
| R2-2110201 | Discussion on survival time state | discussion | NTT DOCOMO INC. | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | ||
| R2-2110227 | Remaining issues on the support of survival time | discussion | Lenovo, Motorola Mobility | NR_IIOT_URLLC_enh-Core | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |
| R2-2110263 | Discussion on the RAN solution for introduction of new QoS parameters | discussion | CMCC | NR_IIOT_URLLC_enh | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |
| R2-2110345 | Finalising Survival Time related enhancements | discussion | Samsung Electronics GmbH |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |||
| R2-2110444 | An Overview of Survival Time Enhancements | discussion | Nokia, Nokia Shanghai Bell | NR_IIOT_URLLC_enh | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |
| R2-2110589 | Consideration on the support of survival time | discussion | OPPO | NR_IIOT_URLLC_enh-Core | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |
| R2-2110673 | Clarification on the survival time requirement |
discussion revision of R2-2108795 |
Xiaomi Communications | NR_IIOT_URLLC_enh-Core | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |
| R2-2110791 | On counting HARQ-NACKs for triggering survival time state | discussion | Futurewei Technologies | NR_IIOT_URLLC_enh-Core | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |
| R2-2110802 | Survival time handling | discussion | Intel Corporation | NR_IIOT_URLLC_enh-Core | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |
| R2-2110913 | Enhancements based on new QoS requirements | discussion | InterDigital | NR_IIOT_URLLC_enh-Core | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |
| R2-2110918 | Issues with UE Survival Time support |
discussion revision of R2-2108457 |
Sequans Communications | NR_IIOT_URLLC_enh-Core | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |
| R2-2110965 | Discussion on RAN enhancement to support survival time | discussion | China Telecommunications |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | |||
| R2-2111167 | Remaining aspects in ST mechanism | discussion | LG Electronics Inc. | NR_IIOT-Core |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] | ||
| R2-2111183 | Discussion of RAN Enhancements to Support Survival Time | discussion | TCL Communication Ltd. | NR_IIOT_URLLC_enh | Rel-17 |
R2-116-e AI: 8.5.4 |
not treated | [WTS] [JSN] |
28 documents (0.33712410926819 seconds)