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-160400 | proposed agenda for RAN2 NB-IOT Ad-hoc Meeting | agenda | MCC |
R2-ah-31965 AI: 2.1 |
approved | [WTS] [JSN] | |||
R2-160401 | LS on NB-IoT Evaluations (R1-157742; contact: Huawei) |
LS in source LS: R1-157742 |
RAN1 | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 3 |
noted | [WTS] [JSN] | |
R2-160402 | LS on S1 signalling solutions for non-NB-IoT UEs (RP-152296; contact: Ericsson) |
LS in source LS: RP-152296 |
RAN | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 3 |
noted | [WTS] [JSN] | |
R2-160403 | LS on NB-IoT (RP-152299; contact: Huawei) |
LS in source LS: RP-152299 |
RAN | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 3 |
noted | [WTS] [JSN] | |
R2-160404 | LS on Extended coverage impact on NAS timers (C1-160739; contact: Ericsson) |
LS in source LS: C1-160739 |
CT1 | Rel-13 |
R2-ah-31965 AI: 3 |
noted | [WTS] [JSN] | ||
R2-160405 | LS on questions on CIoT (C1-160784; contact: Huawei) |
LS in source LS: C1-160784 |
CT1 | Rel-13 |
R2-ah-31965 AI: 3 |
noted | [WTS] [JSN] | ||
R2-160406 | LS on PRACH format (R1-160200; contact: Ericsson) |
LS in source LS: R1-160200 |
RAN1 | Rel-13 |
R2-ah-31965 AI: 3 |
noted | [WTS] [JSN] | ||
R2-160407 | LS on supportable Msg3 size for NB-IoT ( R1-160205; contact: Huawei) |
LS in source LS: R1-160205 |
RAN1 | Rel-13 |
R2-ah-31965 AI: 3 |
noted | [WTS] [JSN] | ||
R2-160408 | Measurement reporting in NB-IOT | discussion | CMCC | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.1 |
noted | [WTS] [JSN] | |
R2-160409 | NB-IoT_system information change notification | discussion | ZTE Corporation | Rel-13 |
R2-ah-31965 AI: 5.3.3 |
noted | [WTS] [JSN] | ||
R2-160410 | Access control of NB-IoT | discussion | ZTE Corporation | Rel-13 |
R2-ah-31965 AI: 5.2 |
available | [WTS] [JSN] | ||
R2-160411 | Paging for NB-IoT | discussion | ZTE Corporation | Rel-13 |
R2-ah-31965 AI: 5.4.3 |
available | [WTS] [JSN] | ||
R2-160412 | Random Access for NB-IoT |
discussion revised to R2-160530 |
ZTE Corporation | Rel-13 |
R2-ah-31965 AI: 6.1 |
revised | [WTS] [JSN] | ||
R2-160413 | NB-IoT Load Distribution Discussion | discussion | ZTE Corporation | Rel-13 |
R2-ah-31965 AI: 5.4.2 |
available | [WTS] [JSN] | ||
R2-160414 | NB-IoT Support for Re-establishment | discussion | ZTE Corporation | Rel-13 |
R2-ah-31965 AI: 5.1.1 |
available | [WTS] [JSN] | ||
R2-160415 | RRC aspects for NB-IoT signaling optimization solution | discussion | ZTE Corporation | Rel-13 |
R2-ah-31965 AI: 5.1.1 |
available | [WTS] [JSN] | ||
R2-160416 | Establishment Cause for NB-IoT | discussion | NTT DOCOMO INC. | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.2 |
available | [WTS] [JSN] | |
R2-160417 | Mobility and measurement considerations | discussion | Gemalto N.V. | Rel-13 |
R2-ah-31965 AI: 5.4.2 |
available | [WTS] [JSN] | ||
R2-160418 | NB-IOT - Paging Enhancements | discussion | MediaTek Inc. | Rel-13 |
R2-ah-31965 AI: 5.4.3 |
available | [WTS] [JSN] | ||
R2-160419 | Further analysis of supporting UP solution by existing RRC states and procedures | discussion | NTT DOCOMO, INC. | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.2 |
available | [WTS] [JSN] | |
R2-160420 | RRC protocol extension for U-plane based solution with AS information stored in RAN (Option 1) | draftCR | NTT DOCOMO, INC. | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.2 |
available | [WTS] [JSN] | |
R2-160421 | RRC protocol extension for U-plane based solution with AS information stored in RAN (Option 2) | draftCR | NTT DOCOMO, INC. | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.2 |
available | [WTS] [JSN] | |
R2-160422 | Some points on the Access Class Barring for the NB-IOT | discussion | Vodafone GmbH | Rel-13 |
R2-ah-31965 AI: 5.2 |
available | [WTS] [JSN] | ||
R2-160423 | Discussion of false paging | discussion | CATT | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.4.3 |
available | [WTS] [JSN] | |
R2-160424 | Discussion on paging enhancements for NB-IoT | discussion | CATT | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.4.3 |
available | [WTS] [JSN] | |
R2-160425 | Creation of 36.331 running CR | discussion | Neul Limited, Huawei, Hisilicon | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.1 |
postponed | [WTS] [JSN] | |
R2-160426 | Miscellaneous aspects for 36.331 | discussion | Neul Limited | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.1 |
noted | [WTS] [JSN] | |
R2-160427 | Scheduling and HARQ principles for NB-IoT | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 6.1 |
postponed | [WTS] [JSN] | |
R2-160428 | Impacts Overview of RAN2 Agreements on Specifications | discussion | Huawei, HiSilicon, Neul | Rel-13 |
R2-ah-31965 AI: 4.1 |
noted | [WTS] [JSN] | ||
R2-160429 | 36.300 Running CR to implement Stage 2 Agreements on NB-IoT |
draftCR revised to R2-160534 |
Huawei | Rel-13 |
R2-ah-31965 AI: 4.3 |
revised | [WTS] [JSN] | ||
R2-160430 | 36.331 Running CR to implement Stage 3 Agreements on NB-IoT | draftCR | Huawei | Rel-13 |
R2-ah-31965 AI: 5.1.1 |
postponed | [WTS] [JSN] | ||
R2-160431 | Discussion on RRC Connection Suspend and Resume | discussion | Huawei, HiSilicon, Neul | Rel-13 |
R2-ah-31965 AI: 5.1.2 |
available | [WTS] [JSN] | ||
R2-160432 | Access Control Enabled Indication | discussion | Huawei, HiSilicon, Neul, CATT | Rel-13 |
R2-ah-31965 AI: 5.2 |
available | [WTS] [JSN] | ||
R2-160433 | System Information Update Notification | discussion | Huawei, HiSilicon, Neul | Rel-13 |
R2-ah-31965 AI: 5.3.3 |
available | [WTS] [JSN] | ||
R2-160434 | Inter-frequency Load Balance | discussion | Huawei, HiSilicon, Neul | Rel-13 |
R2-ah-31965 AI: 5.4.2 |
available | [WTS] [JSN] | ||
R2-160435 | Idle Mode Mobility | discussion | Huawei, HiSilicon, Neul, China Telecom | Rel-13 |
R2-ah-31965 AI: 5.4.2 |
available | [WTS] [JSN] | ||
R2-160436 | DRX in RRC_CONNECTED | discussion | Huawei, HiSilicon, Neul | Rel-13 |
R2-ah-31965 AI: 6.1 |
available | [WTS] [JSN] | ||
R2-160437 | Channel Mapping in MAC layer | discussion | Huawei, HiSilicon, Neul, China Telecom | Rel-13 |
R2-ah-31965 AI: 6.1 |
noted | [WTS] [JSN] | ||
R2-160438 | Consideration on resume failure of UP solution | discussion | ASUSTEK COMPUTER (SHANGHAI) | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.2 |
available | [WTS] [JSN] | |
R2-160439 | Radio Link Failure criteria and procedures | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.1 |
noted | [WTS] [JSN] | |
R2-160440 | RAN impacts to enable CIoT optimizations | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.1 |
available | [WTS] [JSN] | |
R2-160441 | RAN procedure details for CIoT UP solution 18 | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.2 |
available | [WTS] [JSN] | |
R2-160442 | RAN open aspects for CIoT CP solution 2 | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.3 |
available | [WTS] [JSN] | |
R2-160443 | Access control parameters and mechanism | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.2 |
available | [WTS] [JSN] | |
R2-160444 | Idle mode Mobility impacts for NB-IOT | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.4.2 |
available | [WTS] [JSN] | |
R2-160445 | Remaining open aspects on Paging for NB-IOT | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.4.3 |
available | [WTS] [JSN] | |
R2-160446 | Further discussion on RLC-AM for NB-IOT | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 6.2 |
available | [WTS] [JSN] | |
R2-160447 | System Information change | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.3.3 |
available | [WTS] [JSN] | |
R2-160448 | Considerations on Positioning support for NB-IOT | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 4.3 |
noted | [WTS] [JSN] | |
R2-160449 | Idle mode mobility in NB-IoT | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.4.2 |
available | [WTS] [JSN] | |
R2-160450 | Load balancing in NB-IoT | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.4.2 |
available | [WTS] [JSN] | |
R2-160451 | Paging and DRX in Idle mode in NB-IoT | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.4.3 |
available | [WTS] [JSN] | |
R2-160452 | Physical channels for paging in NB-IoT | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.4.3 |
available | [WTS] [JSN] | |
R2-160453 | RLC AM for NB-IOT | discussion | LG Electronics Inc. | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 6.2 |
noted | [WTS] [JSN] | |
R2-160454 | Interaction between solution 2 and 18 | discussion | CATT | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.1 |
noted | [WTS] [JSN] | |
R2-160455 | Discussion on Paging Schemes | discussion | CATT | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.4.3 |
available | [WTS] [JSN] | |
R2-160456 | Remaining requirements for NB-IoT | discussion | Deutsche Telekom AG | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 4.3 |
noted | [WTS] [JSN] | |
R2-160457 | Open issues of SI content | discussion | CATT | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.3.1 |
available | [WTS] [JSN] | |
R2-160458 | Further consideration on solution 2 | discussion | CATT | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.3 |
available | [WTS] [JSN] | |
R2-160459 | RLC-AM in NB-IoT | discussion | CATT | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 6.2 |
available | [WTS] [JSN] | |
R2-160460 | Open Issues of Solution 18 | discussion | CATT | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.2 |
available | [WTS] [JSN] | |
R2-160461 | Considerations on UE capabilities | discussion | Neul, Huawei, HiSilicon | Rel-13 |
R2-ah-31965 AI: 4.2 |
noted | [WTS] [JSN] | ||
R2-160462 | UE capabilities reporting | discussion | Neul, Huawei, HiSilicon | Rel-13 |
R2-ah-31965 AI: 4.2 |
noted | [WTS] [JSN] | ||
R2-160463 | Data transfer procedures for the C-Plane solution | discussion | Neul, Huawei, HiSilicon | Rel-13 |
R2-ah-31965 AI: 5.1.3 |
available | [WTS] [JSN] | ||
R2-160464 | RRC Connection re-establishment in the C-Plane solution | discussion | Neul, Huawei, HiSilicon | Rel-13 |
R2-ah-31965 AI: 5.1.3 |
available | [WTS] [JSN] | ||
R2-160465 | Battery Life Optimisations Analysis | discussion | Neul, Huawei, HiSilicon | Rel-13 |
R2-ah-31965 AI: 6.2 |
noted | [WTS] [JSN] | ||
R2-160466 | Measurement reporting in NB-IOT | draftCR | Ericsson | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.1 |
postponed | [WTS] [JSN] | |
R2-160467 | Measurement reporting in NB-IOT | discussion | Ericsson, China Mobile Com. Corporation | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.1 |
noted | [WTS] [JSN] | |
R2-160468 | SI Scheduling for NB-IoT | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.3.2 |
noted | [WTS] [JSN] | |
R2-160469 | SI Change for NB-IoT | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.3.3 |
available | [WTS] [JSN] | |
R2-160470 | Random access for NB-IoT | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 6.1 |
noted | [WTS] [JSN] | |
R2-160471 | Connected Mode DRX for NB-IoT | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 6.1 |
noted | [WTS] [JSN] | |
R2-160472 | RLC AM/UM Considerations for NB-IoT | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 6.2 |
noted | [WTS] [JSN] | |
R2-160473 | NB-SIB1 design for NB-IoT | discussion | ZTE | Rel-13 |
R2-ah-31965 AI: 5.3.2 |
available | [WTS] [JSN] | ||
R2-160474 | Resume ID | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.2 |
noted | [WTS] [JSN] | |
R2-160475 | RRC Connection Suspend and Resume | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.2 |
available | [WTS] [JSN] | |
R2-160476 | Security aspects of NB-IoT' | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 4.3 |
noted | [WTS] [JSN] | |
R2-160477 | TP for RRC Connection Suspend and Resume | pCR | Ericsson | 36.331 13.0.0 | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.2 |
available | [WTS] [JSN] |
R2-160478 | Access control for NB-IoT | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.2 |
available | [WTS] [JSN] | |
R2-160479 | NB-IOT - RRC connection control | discussion | Ericsson | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.1 |
noted | [WTS] [JSN] | |
R2-160480 | Introduction of NB-IoT functionality to PDCP protocol | draftCR | QUALCOMM INCORPORATED | Rel-13 |
R2-ah-31965 AI: 6.3 |
postponed | [WTS] [JSN] | ||
R2-160481 | NB-IoT RRC connection establishment principles | discussion | QUALCOMM INCORPORATED | Rel-13 |
R2-ah-31965 AI: 5.1.1 |
noted | [WTS] [JSN] | ||
R2-160482 | NB-IoT PDCP transparent mode for data via MME | discussion | QUALCOMM INCORPORATED | Rel-13 |
R2-ah-31965 AI: 6.3 |
noted | [WTS] [JSN] | ||
R2-160483 | NB-IoT cell load management | discussion | QUALCOMM INCORPORATED | Rel-13 |
R2-ah-31965 AI: 5.1.1 |
available | [WTS] [JSN] | ||
R2-160484 | Considerations on PRACH resources for NB-IoT | discussion | Sony | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 6.1 |
noted | [WTS] [JSN] | |
R2-160485 | Access Control for NB-IOT | discussion | Sony | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.2 |
available | [WTS] [JSN] | |
R2-160486 | Implicit Connection Release for NB-IOT | discussion | Sony | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.3 |
available | [WTS] [JSN] | |
R2-160487 | DRX for NB-IOT | discussion | Sony | Rel-13 |
R2-ah-31965 AI: 6.1 |
noted | [WTS] [JSN] | ||
R2-160488 | NB-IOT Measurements for reselection and redirection | discussion | Sony | Rel-13 |
R2-ah-31965 AI: 5.4.2 |
available | [WTS] [JSN] | ||
R2-160489 | AM RLC Simplification for NB-IOT | discussion | Sony | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 6.2 |
noted | [WTS] [JSN] | |
R2-160490 | System Information Area ID and Value Tag | discussion | Sony | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.3.1 |
available | [WTS] [JSN] | |
R2-160491 | “Solution 2”: Queuing of ‘signalling’ behind ‘data via MME’ | discussion | VODAFONE Group Plc | Rel-13 |
R2-ah-31965 AI: 5.1.3 |
noted | [WTS] [JSN] | ||
R2-160492 | RRC connection re-establishment in NB-IoT | discussion | Nokia Networks | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.1 |
available | [WTS] [JSN] | |
R2-160493 | NB-IoT implementation in 3GPP TS 36.304 specification | discussion | Nokia Networks | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.4.1 |
noted | [WTS] [JSN] | |
R2-160494 | NB-IoT – Further details on RRC suspend and resume | discussion | Nokia Networks | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.2 |
available | [WTS] [JSN] | |
R2-160495 | Paging procedure for NB-IoT | discussion | Nokia Networks | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.4.3 |
available | [WTS] [JSN] | |
R2-160496 | Random Access procedure for NB-IoT | discussion | Nokia Networks | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 6.1 |
noted | [WTS] [JSN] | |
R2-160497 | 36.304 running CR to capture agreements on NB-IoT | draftCR | Nokia Networks | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.4.1 |
available | [WTS] [JSN] | |
R2-160498 | RLC-AM Enhancements | discussion | MediaTek Inc. | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 6.2 |
available | [WTS] [JSN] | |
R2-160499 | UE capability design for NB-IoT UEs | discussion | NTT DOCOMO, INC. | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 4.2 |
noted | [WTS] [JSN] | |
R2-160500 | NB-IoT access control | draftCR | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.2 |
available | [WTS] [JSN] | |
R2-160501 | Multi-carrier operation for NB-IOT | discussion | Intel Corporation | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 4.3 |
noted | [WTS] [JSN] | |
R2-160502 | BSR for early transmission of small data | discussion | LG Electronics Inc. | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 6.1 |
noted | [WTS] [JSN] | |
R2-160503 | Early use of DRX cycle for NB-IOT | discussion | LG Electronics Inc. | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 6.1 |
noted | [WTS] [JSN] | |
R2-160504 | RRC configurations with a few default values for NB-IoT | discussion | Sharp | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.3.1 |
available | [WTS] [JSN] | |
R2-160505 | System Information Change and Paging Mechanisms | discussion | INTERDIGITAL COMMUNICATIONS | NB_IOT | Rel-13 |
R2-ah-31965 AI: 5.3.3 |
available | [WTS] [JSN] | |
R2-160506 | NB-IOT - RRC Procedures | discussion | MediaTek Inc. | Rel-13 |
R2-ah-31965 AI: 5.1.1 |
available | [WTS] [JSN] | ||
R2-160507 | NB-IOT - UE Capability and Configuration | discussion | MediaTek Inc. | Rel-13 |
R2-ah-31965 AI: 4.2 |
noted | [WTS] [JSN] | ||
R2-160508 | Discussion on the unique eNB ID for NB-IOT UP solution | discussion | ETRI | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.2 |
available | [WTS] [JSN] | |
R2-160509 | NB-IOT Cell Selection and Reselection | discussion | MediaTek Inc. | Rel-13 |
R2-ah-31965 AI: 5.4.2 |
noted | [WTS] [JSN] | ||
R2-160510 | Discussion on RRC Procedures for CP Solution | discussion | ETRI | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.3 |
available | [WTS] [JSN] | |
R2-160511 | Establishment cause value in Solution 2 and 18 | discussion | NEC | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.1 |
available | [WTS] [JSN] | |
R2-160512 | RRC connection suspend and resume procedures | discussion | NEC | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.2 |
available | [WTS] [JSN] | |
R2-160513 | Need of RRC connection reconfiguration and release in Solution 2 | discussion | NEC | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.3 |
available | [WTS] [JSN] | |
R2-160514 | Report of email discussion on [92#48][NB-IOT] Access Control | report | LG Electronics Inc. | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.2 |
withdrawn | [WTS] [JSN] | |
R2-160515 | Re-use of RRC connection re-establishment procedure for RRC Resume signalling |
discussion revised to R2-161234, R2-161619 |
BlackBerry UK Limited | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.2 |
available | [WTS] [JSN] | |
R2-160516 | Impact on System Information for In-band Operations of NB-IoT | discussion | Samsung Electronics | Rel-13 |
R2-ah-31965 AI: 5.3.1 |
noted | [WTS] [JSN] | ||
R2-160517 | MAC Operation for NB-IoT | discussion | Samsung Electronics | Rel-13 |
R2-ah-31965 AI: 6.1 |
available | [WTS] [JSN] | ||
R2-160518 | Cell Selection and Reselection for NB-IoT | discussion | Samsung Electronics | Rel-13 |
R2-ah-31965 AI: 5.4.2 |
available | [WTS] [JSN] | ||
R2-160519 | Power Saving Paging for NB-IoT | discussion | Samsung Electronics | Rel-13 |
R2-ah-31965 AI: 5.4.3 |
available | [WTS] [JSN] | ||
R2-160520 | Power Ramping Support for NB IoT | discussion | Samsung Electronics | Rel-13 |
R2-ah-31965 AI: 6.1 |
available | [WTS] [JSN] | ||
R2-160521 | Specifying solution 2 in the AS specification | discussion | Samsung Electronics | Rel-13 |
R2-ah-31965 AI: 5.1.3 |
available | [WTS] [JSN] | ||
R2-160522 | RRC aspects of Suspend/Resume Procedure | discussion | Samsung Electronics | Rel-13 |
R2-ah-31965 AI: 5.1.2 |
noted | [WTS] [JSN] | ||
R2-160523 | Discussions on access control for NB-IoT | discussion | Samsung Electronics | Rel-13 |
R2-ah-31965 AI: 5.2 |
available | [WTS] [JSN] | ||
R2-160524 | Report of email discussion on [92#48][NB-IOT] Access Control | report | LG Electronics France | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.2 |
noted | [WTS] [JSN] | |
R2-160525 | System information change in NB-IoT | discussion | LG Electronics Inc. | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.3.3 |
available | [WTS] [JSN] | |
R2-160526 | UP modelling for U-plane solution | discussion | NTT DOCOMO INC. | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.2 |
available | [WTS] [JSN] | |
R2-160527 | The detailed procedure of solution 18 | discussion | LG Electronics France | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.1.2 |
available | [WTS] [JSN] | |
R2-160528 | Measurement rules for cell reselection in NB-IoT | discussion | LG Electronics France | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.4.2 |
available | [WTS] [JSN] | |
R2-160529 | Cell Reselection in NB-IoT | discussion | LG Electronics France | NB_IOT-Core | Rel-13 |
R2-ah-31965 AI: 5.4.2 |
available | [WTS] [JSN] | |
R2-160530 | Random Access for NB-IoT |
discussion revision of R2-160412 |
ZTE Corporation | Rel-13 |
R2-ah-31965 AI: 6.1 |
noted | [WTS] [JSN] | ||
R2-160531 | Draft reply LS on questions on CIoT (to: CT1; cc: SA2, RAN1, CT4; contact: Huawei) |
LS out revised to R2-160535 |
Huawei | Rel-13 |
R2-ah-31965 AI: 3 |
revised | [WTS] [JSN] | ||
R2-160532 | LS on NB-MIB (R1-160220; contact: Huawei) | LS in | RAN1 | Rel-13 |
R2-ah-31965 AI: 3 |
noted | [WTS] [JSN] | ||
R2-160533 | WF on Positioning support for NB-IOT | discussion | CMCC | Rel-13 |
R2-ah-31965 AI: 4.3 |
noted | [WTS] [JSN] | ||
R2-160534 | 36.300 Running CR to implement Stage 2 Agreements on NB-IoT |
draftCR revision of R2-160429 |
Huawei | Rel-13 |
R2-ah-31965 AI: 4.3 |
postponed | [WTS] [JSN] | ||
R2-160535 | Draft reply LS on questions on CIoT (to: CT1; cc: SA2, RAN1, CT4; contact: Huawei) |
LS out revision of R2-160531 revised to R2-160536 |
Huawei | Rel-13 |
R2-ah-31965 AI: 3 |
revised | [WTS] [JSN] | ||
R2-160536 | Reply LS on questions on CIoT (to: CT1; cc: SA2, RAN1, CT4; contact: Huawei) |
LS out revision of R2-160535 |
RAN2 | Rel-13 |
R2-ah-31965 AI: 3 |
approved | [WTS] [JSN] |
137 documents (1.0644459724426 seconds)