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-1816459 | Discussion on Handling CN Overload Issue for eLTE |
discussion revised to R2-1818556 |
OPPO | Rel-15 |
R2-104 AI: 9.7.2 |
revised | [WTS] [JSN] | ||
| R2-1817246 | delayTolerantAccess is not used with E-UTRA/5GC | CR | Nokia, Nokia Shanghai Bell | 36.331 15.3.0 CR#3742 catF | LTE_5GCN_connect | Rel-15 |
R2-104 AI: 9.7.2 |
not treated | [WTS] [JSN] |
| R2-1817310 | CN differentiation in MSG3 | discussion | Ericsson | LTE_5GCN_connect-Core | Rel-15 |
R2-104 AI: 9.7.2 |
noted | [WTS] [JSN] | |
| R2-1817311 | Supporting MME and AMF overload control |
CR revised to R2-1818691 |
Ericsson | 36.331 15.3.0 CR#3745 catF | LTE_5GCN_connect-Core | Rel-15 |
R2-104 AI: 9.7.2 |
revised | [WTS] [JSN] |
| R2-1817547 | CR on Handling CN Overload in eLTE | CR | OPPO | 36.3 15.3.0 CR#1204 catF | LTE_5GCN_connect | Rel-15 |
R2-104 AI: 9.7.2 |
not treated | [WTS] [JSN] |
| R2-1817562 | [Draft] Reply LS on Handling CN Overload in eLTE |
LS out LS To: SA2 revised to R2-1818557 |
OPPO | Rel-15 |
R2-104 AI: 9.7.2 |
revised | [WTS] [JSN] | ||
| R2-1817806 | Restore CN Overload Control capability with Option 5 enabled eNB | CR | VODAFONE Group Plc | 36.331 15.3.0 CR#3777 catF | LTE_5GCN_connect-Core | Rel-15 |
R2-104 AI: 9.7.2 |
not treated | [WTS] [JSN] |
| R2-1818091 | Correction on UERadioPagingInformation for LTE-5GC | CR | Huawei, HiSilicon | 36.331 15.3.0 CR#3788 catF | LTE_5GCN_connect-Core | Rel-15 |
R2-104 AI: 9.7.2 |
not pursued | [WTS] [JSN] |
| R2-1818092 | Discussion on RRC establishment cause for LTE-5GC | discussion | Huawei, HiSilicon | LTE_5GCN_connect-Core | Rel-15 |
R2-104 AI: 9.7.2 |
noted | [WTS] [JSN] | |
| R2-1818093 | Correction on the usage of delayTolerantAcess | CR | Huawei, HiSilicon | 36.331 15.3.0 CR#3789 catF | LTE_5GCN_connect-Core | Rel-15 |
R2-104 AI: 9.7.2 |
agreed | [WTS] [JSN] |
| R2-1818094 | Correction to full configuration for LTE-5GC | CR | Huawei, HiSilicon | 36.331 15.3.0 CR#3790 catF | LTE_5GCN_connect-Core | Rel-15 |
R2-104 AI: 9.7.2 |
not treated | [WTS] [JSN] |
| R2-1818095 | Considerations on scheduling and overload issues for LTE-5GC | CR | Huawei, HiSilicon | 36.331 15.3.0 CR#3791 catF | LTE_5GCN_connect-Core | Rel-15 |
R2-104 AI: 9.7.2 |
not treated | [WTS] [JSN] |
| R2-1818096 | Clarification on UE behavior after handover failure | CR | Huawei, HiSilicon | 36.331 15.3.0 CR#3792 catF | LTE_5GCN_connect-Core | Rel-15 |
R2-104 AI: 9.7.2 |
postponed | [WTS] [JSN] |
| R2-1818097 | Clarification on Security Handling during RRC reestablishment due to N2 Handover Failure | CR | Huawei, HiSilicon | 36.331 15.3.0 CR#3793 catF | LTE_5GCN_connect-Core | Rel-15 |
R2-104 AI: 9.7.2 |
not pursued | [WTS] [JSN] |
| R2-1818556 | Discussion on Handling CN Overload Issue for eLTE |
discussion revision of R2-1816459 |
OPPO | Rel-15 |
R2-104 AI: 9.7.2 |
noted | [WTS] [JSN] | ||
| R2-1818557 | [Draft] Reply LS on Handling CN Overload in eLTE |
LS out LS To: SA2 revision of R2-1817562 |
OPPO | Rel-15 |
R2-104 AI: 9.7.2 |
not treated | [WTS] [JSN] | ||
| R2-1818691 | Supporting MME and AMF overload control |
CR revision of R2-1817311 revised to R2-1819188 |
Ericsson | 36.331 15.3.0 CR#37451 catF | LTE_5GCN_connect-Core | Rel-15 |
R2-104 AI: 9.7.2 |
revised | [WTS] [JSN] |
| R2-1819188 | Supporting MME and AMF overload control |
CR revision of R2-1818691 |
Ericsson | 36.331 15.3.0 CR#37452 catF | LTE_5GCN_connect-Core | Rel-15 |
R2-104 AI: 9.7.2 |
agreed | [WTS] [JSN] |
18 documents (0.32274699211121 seconds)