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-162314 | 36.331 Running CR to Capture Agreements on NB-IoT | draftCR | Huawei | Rel-14 |
R2-93 AI: 7.14.2.1 |
not pursued | [WTS] [JSN] | ||
| R2-162315 | 36.331 Running CR including ASN.1 | draftCR | Huawei | Rel-14 |
R2-93 AI: 7.14.2.1 |
not pursued | [WTS] [JSN] | ||
| R2-162316 | 36.331 Running CR Implementation | discussion | Huawei, HiSilicon, Neul |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |||
| R2-162317 | Email Discussion Report on [93#40][NB-IOT] ASN.1 Structure | discussion | Huawei |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |||
| R2-162318 | ASN.1 Structure Using Multiple Modules | discussion | Huawei |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |||
| R2-162319 | Report of the unofficial email discussion on ASN.1 for dedicated radio resource configuration | discussion | Huawei |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |||
| R2-162320 | Report of the email discussion [93#43][NB-IOT] CP Solution | discussion | Huawei |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |||
| R2-162321 | RRC Remaining Issues | discussion | Huawei, HiSilicon, Neul |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |||
| R2-162322 | PHY Configuration - ASN.1 aspects | discussion | Huawei, HiSilicon, Neul |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |||
| R2-162323 | Radio Link Failure | discussion | Huawei, HiSilicon, Neul |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |||
| R2-162324 | Terminology for NB-IoT Solution 18 | discussion | Huawei, HiSilicon, Neul |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |||
| R2-162355 | Msg3 in NB-IoT | discussion | ZTE | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162356 | Remaining issues for UP solution | discussion | ZTE | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162357 | Considerations on cIoT indications in NB-IoT | discussion | ZTE | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162483 | Discussion on dedicated SR for NB-IoT | discussion | NTT DOCOMO INC. | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162485 | UP modelling for U-plane solution |
discussion revision of R2-161332 |
NTT DOCOMO INC. | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162493 | RRC structure for NB-IOT | discussion | Nokia, Alcatel-Lucent Shanghai Bell | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162506 | Report of the email discussion [93#41][NB-IOT] Resume operation | discussion | Ericsson | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | ||
| R2-162543 | CIoT indications in SIB and msg.5 during attach procedure for NB-IOT | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162545 | RAN impacts of CIoT CP and UP solution for NB-IOT | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162550 | Remaining aspects of message 3 for NB-IoT | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162552 | Open aspects of UP solution for NB-IoT | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162554 | Need of NAS recovery and RLF/RLM triggering | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162557 | Response to SA2 on RRC establishment cause | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162559 | Bearer id list in Resume message 3 for NB-IoT | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |
| R2-162596 | Further discussion on NB-IoT resume failure | discussion | HTC Corporation | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |
| R2-162597 | Discussion on RRC connection setup handling in RRC connection resume procedure | discussion | HTC Corporation | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |
| R2-162598 | Consideration on open issues of resumption | discussion | CATT | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |
| R2-162599 | How to construct the volume indication | discussion | CATT | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |
| R2-162634 | Considerations on Resume ID | discussion | Sony | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162644 | NB-IoT – Further details on RRC suspend and resume | discussion | Nokia, Alcatel-Lucent Shanghai Bell | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |
| R2-162645 | Solution preference and data volume indications for NB-IoT | discussion | Nokia, Alcatel-Lucent Shanghai Bell | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162658 | Issues Related to Non- anchor PRB | discussion | SHARP Corporation |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |||
| R2-162659 | NAS Recovery for NB-IoT UE | discussion | NTT DOCOMO INC. | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162661 | Necessary IEs in message 3 | discussion | NTT DOCOMO INC. | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162679 | UE capabilities | discussion | Ericsson | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | ||
| R2-162680 | Introduction of NB-IoT UE capabilities | draftCR | Ericsson | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | ||
| R2-162681 | Access Barring | discussion | Ericsson | Rel-13 |
R2-93 AI: 7.14.2.1 |
postponed | [WTS] [JSN] | ||
| R2-162682 | Access Barring | draftCR | Ericsson | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | ||
| R2-162683 | Establishment causes for NB-IoT | discussion | Ericsson | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | ||
| R2-162692 | Draft CR to capture outcome of mail discussion on RRC Resume operation | draftCR | Ericsson | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | ||
| R2-162736 | Early RRC Connection Release for UP solution | discussion | Sequans Communications | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |
| R2-162769 | UE Reconfiguration to a Non-Anchor Carrier in NB-IoT | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162828 | RRC Connection Release for CP solution | discussion | Sequans Communications | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |
| R2-162829 | Autonomous RRC Connection Release | discussion | Sequans Communications | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |
| R2-162856 | Introducing SRB3 for NB-IOT | discussion | LG Electronics Inc. | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162857 | Need for PDCP TM in NB-IOT | discussion | LG Electronics Inc. | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162865 | RRC Resume AS-NAS interaction | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |
| R2-162866 | Security aspects of NB-IoT | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162867 | Further aspects of RRC Resume and Resume Id | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |
| R2-162871 | Release Cause Indication at RLF | discussion | LG Electronics France | NB_IOT-Core |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | ||
| R2-162880 | NB-IOT – Remaining RRC Issues | discussion | MediaTek Inc. | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | ||
| R2-162886 | Simultaneous support of CP and UP solutions | discussion | NEC | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162887 | Procedure for mo-Signaling after RRC suspended | discussion | NEC | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |
| R2-162900 | Data Volume Indicator for NB-IOT | discussion | LG Electronics Inc. | NB_IOT-Core |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | ||
| R2-162918 | ata Volume Indication Mechanism in NB-IoT | discussion | Samsung Electronics |
R2-93 AI: 7.14.2.1 |
reserved | [WTS] [JSN] | |||
| R2-162921 | Data Volume Indication Mechanism in NB-IoT | discussion | Samsung Electronics |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |||
| R2-162937 | Access Barring Alleviation for NB-IOT | discussion | LG Electronics Inc. | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |
| R2-162938 | The reject procedure of RRC connection resume request in solution 18 | discussion | LG Electronics Inc. | NB_IOT | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |
| R2-162939 | UE internal NAS-AS interaction to perform RRC connection resume procedure | discussion | LG Electronics Inc. | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |
| R2-162948 | Email Report of [93#42][NB-IOT] Access Control | report | LG Electronics Inc. | NB_IOT-Core |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | ||
| R2-162950 | Proposed CR to 36.331 on NB-IOT access control | draftCR | LG Electronics Inc. | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
available | [WTS] [JSN] | |
| R2-162968 | Comments on 36.331 Running CR to capture agreements on NB-IoT | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
noted | [WTS] [JSN] | |
| R2-162969 | 36.331 CR to capture introduction of NB-IoT | draftCR | Ericsson | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
not pursued | [WTS] [JSN] | |
| R2-163041 | DRAFT LS on Security Aspects for NB-IoT (to: SA3; cc: -; contact: ZTE) |
LS out revised to R2-163129 |
ZTE Corporation | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
revised | [WTS] [JSN] | |
| R2-163051 | Draft LS latest updates about access control for NB-IOT in RAN2 |
LS out revised to R2-163122 |
LGE | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
revised | [WTS] [JSN] | |
| R2-163054 | 36.331 36.331 Running CR to capture agreements on NB-IoT | draftCR | Huawei | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
endorsed | [WTS] [JSN] | |
| R2-163122 | LS latest updates about access control for NB-IOT in RAN2 (to: CT1; cc: -; contact: LGE) |
LS out revision of R2-163051 |
RAN2 | NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
approved | [WTS] [JSN] | |
| R2-163126 | [DRAFT] LS on CIoT agreements for non-NB-IoT and for the bearer suspended list (to: CT1, SA2, RAN3; cc: CT4; contact: Intel) |
LS out revised to R2-163149 |
Intel Corporation | TEI13, NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
revised | [WTS] [JSN] | |
| R2-163129 | LS on Security Aspects for NB-IoT (to: SA3; cc: -; contact: ZTE) |
LS out revision of R2-163041 |
RAN2 | NB_IOT-Core, TEI13 | Rel-13 |
R2-93 AI: 7.14.2.1 |
approved | [WTS] [JSN] | |
| R2-163149 | LS on CIoT agreements for non-NB-IoT and for the bearer suspended list (to: CT1, SA2, RAN3; cc: CT4; contact: Intel) |
LS out revision of R2-163126 |
RAN2 | TEI13, NB_IOT-Core | Rel-13 |
R2-93 AI: 7.14.2.1 |
approved | [WTS] [JSN] |
71 documents (0.36430501937866 seconds)