3GPP TDocs (written contributions) at meeting
Meeting: R3-69b - 2010-10-11 to 2010-10-15, Xi'an
meeting id: R3-69b (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
R3‑102554 | Agenda for RAN3#69bis, Xi'an, China | Chairman | Approved |
R3‑102555 | RAN3#69 Meeting Report, Madrid, Spain | MCC | Approved |
R3‑102556 | TR 30.531 for information | MCC | Noted |
R3‑102557 | Inclusion of the “RRC Establishment Cause” in the “(RANAP) Initial UE message” (Source: CT1; To: RAN3, SA2; Cc: RAN2) | CT1 | Noted |
R3‑102558 | LS on Transfer of SPID during (inter-RAT) handover (Source: GERAN2; To: CT1, CT4; Cc: RAN3, SA2) | GERAN2 | Noted |
R3‑102559 | LS on Enhancements of Iur-g interface (Source: GERAN; To: RAN3; Cc: RAN) | GERAN | Noted |
R3‑102560 | Reply LS on intra-eNB energy saving solutions (Source: RAN1; To: RAN2; Cc: RAN3, RAN4) | RAN1 | Noted |
R3‑102561 | LS on eICIC progress in RAN1 (Source: RAN1; To: RAN, RAN2, RAN3, RAN4) | RAN1 | Noted |
R3‑102562 | LS on draft RAN1 CRs for Carrier Aggregation, Enhanced Downlink Multiple Antenna Transmission and Uplink Multiple Antenna Transmission Work Items (Source: RAN1; To: RAN2, RAN3, RAN4; Cc: RAN) | RAN1 | Noted |
R3‑102563 | Reply LS on Support for different HS-SCCHs in contiguous TTIs in CELL_FACH (Source: RAN2; To: RAN1, RAN3) | RAN2 | Noted |
R3‑102564 | Response LS to R2-104233_S3-100901 on enhancing AS security (Source: RAN2; To: SA3; Cc: RAN3, SA5) | RAN2 | Noted |
R3‑102565 | Considerations on counting for MBMS activation (Source: RAN2; To: RAN3, SA2) | RAN2 | Noted |
R3‑102566 | Reply LS on MDT configuration for IDLE mode UE (Source: RAN2; To: SA5; Cc: RAN3) | RAN2 | Noted |
R3‑102567 | SRB only PS Handover (Source: RAN2; To: SA2, CT4; Cc: RAN3, RAN5) | RAN2 | Noted |
R3‑102568 | LS on RN testing (Source: RAN2; To: RAN; Cc: RAN1, RAN3, RAN4, RAN5) | RAN2 | Noted |
R3‑102569 | LS on Interaction with Trace for MDT (Source: RAN2; To: SA5; Cc: RAN3) | RAN2 | Noted |
R3‑102570 | Reply LS on 4C-HSDPA capabilities (Source: RAN4; To: RAN2; Cc: RAN1, RAN3) | RAN4 | Noted |
R3‑102571 | Reply LS to on Enhancements of Iur-g interface (Source: RAN; To: GERAN, RAN3, GERAN2, RAN2; Cc: SA) | RAN | Noted |
R3‑102572 | LS on GERAN and UTRAN handling of RFSP Index/SPID (Source: SA2; To: GERAN2, RAN3; Cc: CT1) | SA2 | Noted |
R3‑102573 | Reply LS on Inclusion of the “RRC Establishment Cause” in the “(RANAP) Initial UE message” (Source: SA2; To: CT1; Cc: RAN3, RAN2) | SA2 | Noted |
R3‑102574 | LS on PS handover failure during the SRVCC (Source: SA2; To: RAN2, RAN3, GERAN2) | SA2 | Noted |
R3‑102575 | LS on Release 10 NIMTC Conclusion (Source: SA2; To: GERAN, GERAN2, CT1, CT4, SA1, SA3, SA5, RAN2, RAN3) | SA2 | Noted |
R3‑102576 | LS on new Study Item on Core Network Overload issues (Source: SA2; To: RAN2, RAN3, GERAN, GERAN2, CT1, CT4, SA3; Cc: SA, SA1) | SA2 | Noted |
R3‑102577 | LS on Access Delay estimation for RACH Optimization (Source: SA5; To: RAN2; Cc: RAN3) | SA5 | Noted |
R3‑102578 | LS on Relay Node Security (Source: SA; To: SA3; Cc: RAN, RAN2, RAN3, CT, CT1, CT4) | SA | Noted |
R3‑102579 | LS on Remaining work for LIPA completion (Source: SA; To: SA3, RAN3; Cc: RAN, SA2) | SA | Noted |
R3‑102580 | Discussion on MBMS Status Report | New Postcom | Noted |
R3‑102581 | Issues on MBMS Pre-emption | New Postcom | Noted |
R3‑102582 | Discussion on GUMMEI handling in S1 Setup Response | New Postcom | Noted |
R3‑102583 | Neighbour relationship handling for handover type decision | New Postcom | Noted |
R3‑102584 | ECGI configuration for RN | New Postcom | Noted |
R3‑102585 | Non-UE associated S1/X2 procedure handling in DeNB | New Postcom | Not Treated |
R3‑102586 | Correction of Inter-system SRVCC | Huawei | Agreed |
R3‑102587 | Correction of Inter-system SRVCC | Huawei | Agreed |
R3‑102588 | Clarification on downlink power balancing | Huawei | Not Agreed |
R3‑102589 | Clarification on downlink power balancing | Huawei | Not Agreed |
R3‑102590 | Clarification on downlink power balancing | Huawei | Not Agreed |
R3‑102591 | Clarification on downlink power balancing | Huawei | Not Agreed |
R3‑102592 | Clarification on downlink power balancing | Huawei | Not Agreed |
R3‑102593 | Clarification on downlink power balancing | Huawei | Not Agreed |
R3‑102594 | UE EDRX deactivation | Huawei | Noted |
R3‑102595 | Addition of common E-DCH resource information report | Huawei | Postponed |
R3‑102596 | Paging based on UE Subscriber Information | Huawei, HiSilicon | Postponed |
R3‑102597 | X2 setup between macro eNB and HeNB-GW | Motorola | Not Treated |
R3‑102598 | GW selection for RN | Motorola, Samsung | Noted |
R3‑102599 | GW selection for RN | Motorola, Samsung | Not Treated |
R3‑102600 | Clean up on S1 related text in C-Plane Handling section | Motorola | Not Treated |
R3‑102601 | MME Overload handling in relay deployment | Motorola | Noted |
R3‑102602 | Offline report on Neighboring cell handling and HO Type determination | Motorola, New Postcom, CATT | Noted |
R3‑102603 | Clarify the criteria for S1 HO and X2 HO related to Relay | Motorola, New Postcom, CATT | Revised |
R3‑102604 | X2 setup between DeNB and eNB | Motorola | Not Treated |
R3‑102605 | Add TAI for neighbour cell in X2 Setup procedure and eNB Configuration Update procedure | Motorola | Not Treated |
R3‑102606 | No NNSF function in RN | Motorola | Not Treated |
R3‑102607 | Transport layer address handling for S1 message and X2 message in DeNB | Motorola | Not Treated |
R3‑102608 | Deactivate and Activate the MBMS service based on the reception status report | Motorola | Noted |
R3‑102609 | Discussion on non-UE Dedicated X2-AP Messages Handling | Fujitsu | Not Treated |
R3‑102610 | Discussion on Handling of Neighbour Relation in Relays | Fujitsu | Not Treated |
R3‑102611 | Solutions to HeNB addressing issue | New Postcom | Noted |
R3‑102612 | Issues on X2-based mobility for HeNBs from ANR perspective | New Postcom | Not Treated |
R3‑102613 | Measurement framework support for detection of short-stay problems | New Postcom | Not Treated |
R3‑102614 | Detection method for the short-stay problems | New Postcom | Not Treated |
R3‑102615 | Advertisement of MME’s support of Relays | New Postcom | Postponed |
R3‑102616 | Introduction of MC-HSUPA for 1.28Mcps TDD | TD Tech | Revised |
R3‑102617 | Discussion on standalone midamble channel in MU-MIMO for 1.28Mcps TDD | TD Tech | Noted |
R3‑102618 | ECGI Configuration for Cells under RN | Potevio | Noted |
R3‑102619 | The Overview of SITPO in R10 | Huawei | Noted |
R3‑102620 | The Introduction for SIPTO at Iu-PS for UMTS | Huawei | Noted |
R3‑102621 | Introduction of TOF as a function | Huawei | Not Treated |
R3‑102622 | Introduction of TOF as a function | Huawei | Not Treated |
R3‑102623 | Introduction of TOF as a function | Huawei | Not Treated |
R3‑102624 | Introduction of TOF as a function | Huawei | Not Treated |
R3‑102625 | Introduction of TOF as a logical node | Huawei | Revised |
R3‑102626 | Introduction of TOF as a logical node | Huawei | Revised |
R3‑102627 | Introduction of TOF as a logical node | Huawei | Revised |
R3‑102628 | Operating mode Switch of dual cell and MIMO | Huawei | Noted |
R3‑102629 | Operating mode Switch of dual cell and MIMO | Huawei | Not Treated |
R3‑102630 | Operating mode Switch of dual cell and MIMO | Huawei | Not Treated |
R3‑102631 | Analysis on the X2 setup between HeNB and (H)eNB based on X2GW | Huawei | Not Treated |
R3‑102632 | Discussion on the Mobility Enhancement between HeNB and eNB | Huawei | Not Treated |
R3‑102633 | Discussion on the Access Control for CELL_FACH Mobility | Huawei | Noted |
R3‑102634 | Discussion on U-RNTI Management | Huawei | Not Treated |
R3‑102635 | Correction on the Functional Split Table of MOCN | Huawei | Agreed |
R3‑102636 | Clarification on Handover Restriction List | Huawei, Nokia Siemens Networks, NTT DoCoMo, INC. | Revised |
R3‑102637 | Clarification on Handover Restriction List | Huawei, Nokia Siemens Networks, NTT DoCoMo, INC. | Revised |
R3‑102638 | Clarification on definition of MMEC | Huawei | Revised |
R3‑102639 | Prioirity handling for eMPS Paging | Huawei | Noted |
R3‑102640 | [DRAFT] Reply LS on MBMS Reception Status Counting (To: RAN2) | Huawei | Revised |
R3‑102641 | Support of ARP Pre-emption | Huawei, CATT, CMCC | Noted |
R3‑102642 | Support of ARP Pre-emption | Huawei | Noted |
R3‑102643 | Support of ARP Pre-emption | Huawei | Not Treated |
R3‑102644 | MBMS Reception Status Counting | Huawei | Noted |
R3‑102645 | MBMS Reception Status Counting | Huawei | Not Treated |
R3‑102646 | MBMS Reception Status Counting | Huawei | Not Treated |
R3‑102647 | MBMS procedure for MBR greater than GBR | Huawei | Noted |
R3‑102648 | CA impact on RAN3 | Huawei | Noted |
R3‑102649 | The GW selection for RN | Huawei | Noted |
R3‑102650 | Add X2 eNB Configuration Update procedure in RN attachment | Huawei | Revised |
R3‑102651 | TNL address mapping | Huawei | Not Treated |
R3‑102652 | TNL address mapping | Huawei | Not Treated |
R3‑102653 | Remaining Issues on RN Indication | Huawei | Noted |
R3‑102654 | Relay Node Un Signalling Transport Support | Huawei | Not Treated |
R3‑102655 | Signalling Transport for Relay Node Support | Huawei | Not Treated |
R3‑102656 | Signalling Transport for Relay Node Support | Huawei | Not Treated |
R3‑102657 | S1 non UE associated msg handling | Huawei | Noted |
R3‑102658 | S1 non UE associated msg handling | Huawei | Revised |
R3‑102659 | S1 handover routing toward RN | Huawei | Not Treated |
R3‑102660 | Way forward for overload control of MTC Devices | Huawei, HiSilicon, LG Electronics | Noted |
R3‑102661 | Introduce overload control mechanism for MTC Devices | Huawei, HiSilicon | Not Treated |
R3‑102662 | Dedicated CN node for MTC Device | Huawei, HiSilicon, LG Electronics | Not Treated |
R3‑102663 | A method to avoid CN overload due to Machine-Type Communications | Huawei, HiSilicon, LG Electronics | Not Treated |
R3‑102664 | Introduction of LIPA Functions for UMTS | Alcatel-Lucent | Not Treated |
R3‑102665 | Introduction of LIPA Functions for UMTS | Alcatel-Lucent | Not Treated |
R3‑102666 | Introduction of LIPA Functions for UMTS | Alcatel-Lucent | Noted |
R3‑102667 | Introduction of MTC overload protection | Alcatel-Lucent | Not Treated |
R3‑102668 | Introduction of MTC Overload support | Alcatel-Lucent | Not Treated |
R3‑102669 | MTC Overload Considerations | Alcatel-Lucent | Noted |
R3‑102670 | Addition of HNB-GW Status procedure. | Alcatel-Lucent, ip.access | Revised |
R3‑102671 | Text Proposal for HRNSAP | Alcatel-Lucent | Revised |
R3‑102672 | Additional messages to support HNB-HNB HO in HNBAP | Alcatel-Lucent | Postponed |
R3‑102673 | URNTI management within the HNB RAN | Alcatel-Lucent | Not Treated |
R3‑102674 | Issues related to Cell FACH support for HNB Handover. | Alcatel-Lucent | Not Treated |
R3‑102675 | Cell FACH support for HNB Handover | Alcatel-Lucent | Not Treated |
R3‑102676 | Introduction of Cell_Update procedure. | Alcatel-Lucent | Not Treated |
R3‑102677 | Introduction of HNB to HNB Cell_FACH mobility procedure using direct interface. | Alcatel-Lucent | Not Treated |
R3‑102678 | Additional messages to support CELL_FACH mobility in HNBAP | Alcatel-Lucent | Not Treated |
R3‑102679 | Scaling issues for SABP and ETWS. | Alcatel-Lucent | Noted |
R3‑102680 | RNC selection of SPID | Telecom Italia | Not Agreed |
R3‑102681 | RNC selection of SPID | Telecom Italia | Not Agreed |
R3‑102682 | Consideration on O&M requirement | CATT | Noted |
R3‑102683 | Discussion on how DeNB identifies the RN from CN | CATT | Noted |
R3‑102684 | Impact on GW selection by different phases of RN startup procedure | CATT, CMCC | Noted |
R3‑102685 | Handling of the MME Direct Information Transfer message | CATT | Noted |
R3‑102686 | ANR handling for RN | CATT | Not Treated |
R3‑102687 | Self-configuration handling for RN | CATT | Not Treated |
R3‑102688 | MME addressing during X2 HO | CATT | Not Treated |
R3‑102689 | X2 connectivity information for RN | CATT | Not Treated |
R3‑102690 | X2 connectivity information for RN | CATT | Not Treated |
R3‑102691 | GUMMEI information for handover type determination | CATT | Not Treated |
R3‑102692 | How to map UE EPS bearers to Un bearers | CATT | Not Treated |
R3‑102693 | Clarification on E-PUCH transmision power in enhanced CELL_FACH | CATT | Withdrawn |
R3‑102694 | Clarification on E-PUCH transmision power in enhanced CELL_FACH | CATT | Withdrawn |
R3‑102695 | Introduction of MC-HSUPA to RNSAP | CATT | Revised |
R3‑102696 | Introduction of MC-HSUPA to NBAP | CATT | Revised |
R3‑102697 | Impact analysis on RAN3 specifications for MU-MIMO | CATT | Noted |
R3‑102698 | Introduction of MU-MIMO to RNSAP | CATT | Revised |
R3‑102699 | Introduction of MU-MIMO to NBAP | CATT | Revised |
R3‑102700 | Introduction of MU-MIMO to CTCH of Iur user plane | CATT | Not Treated |
R3‑102701 | Introduction of MU-MIMO to CTCH of Iub user plane | CATT | Not Treated |
R3‑102702 | The counting procedure in M2 interface | CATT | Noted |
R3‑102703 | Discussion on MTC Overload Indication | CATT | Noted |
R3‑102704 | Discussion on routing X2AP messages with X2-GW | CATT | Not Treated |
R3‑102705 | Add the function of routing X2AP message to HeNB-GW | CATT | Not Treated |
R3‑102706 | Open issues in X2 setup procedure between HeNBs | CATT | Not Treated |
R3‑102707 | Add a new cause value for X2 setup failure | CATT | Not Treated |
R3‑102708 | Discussion on overload procedure for HeNBs | CATT | Noted |
R3‑102709 | Additional information in overload procedure | CATT | Not Treated |
R3‑102710 | Content extension of RLF report for MRO | CATT | Not Treated |
R3‑102711 | Inter-RAT MLB scenario and parameters coordination | CATT | Noted |
R3‑102712 | Discussion on coordination of energy saving parameters | CATT | Noted |
R3‑102713 | IRAT too late | Huawei | Noted |
R3‑102714 | Text proposal for 3.023 on IRAT too Late | Huawei | Not Treated |
R3‑102715 | Draft LS for IRAT too late | Huawei | Not Treated |
R3‑102716 | Rapid HO | Huawei | Not Treated |
R3‑102717 | Text proposal for 3.023 on Rapid HO | Huawei | Not Treated |
R3‑102718 | eNB behaviour for generation of RLF INDICATION | Huawei | Not Treated |
R3‑102719 | Active mode Inter RAT Ping-Pong | Huawei | Revised |
R3‑102720 | Events for MLB | Huawei | Noted |
R3‑102721 | RLF report from idle | Huawei | Not Treated |
R3‑102722 | Uplink Signaling required for Network Based Positioning | Andrew Corp | Noted |
R3‑102723 | NAS tx not necessary if E-RAB unknown at eNB | Motorola, KDDI | Noted |
R3‑102724 | NAS-PDU not sent to UE if E-RAB ID unknown during E-RAB Release cmd | Motorola, KDDI | Revised |
R3‑102725 | Clarification for setting AP IDs in the Error Indication msg and incorrect causes | Motorola | Revised |
R3‑102726 | Clarification for setting the AP IDs in Error Indication msg | Motorola | Revised |
R3‑102727 | Specify what are the first messages, first returned messages and the last messages | Motorola | Not Agreed |
R3‑102728 | Max number of Cell IDs in Write Replace Warning msg | Motorola | Noted |
R3‑102729 | Corrections on LPPa message transfer in 36.305 | HTC | Postponed |
R3‑102730 | - | - | - |
R3‑102731 | Consideration on MBR larger than GBR | ZTE | Noted |
R3‑102732 | - | - | - |
R3‑102733 | CR for MBMS User Data flow synchronisation | ZTE | Not Treated |
R3‑102734 | Two-Phrase RN Start-up Procedure | ZTE | Not Treated |
R3‑102735 | DeNB based ECGI configuration | ZTE | Noted |
R3‑102736 | How RN learns the X2 availability between DeNB and Neigbour eNB | ZTE | Noted |
R3‑102737 | PDN connection for RN’s OAM Traffic | ZTE | Noted |
R3‑102738 | Discussion on MME Pool Requirements for HeNB GW | ZTE | Not Treated |
R3‑102739 | ANRF for UTRAN | ZTE, China Unicom | Not Treated |
R3‑102740 | Intra-UTRAN ANR with Iur | ZTE | Not Treated |
R3‑102741 | The way forward issues for UTRAN ANR | ZTE, China Unicom | Noted |
R3‑102742 | The supplement of the UE-originated RLF reporting | ZTE | Not Treated |
R3‑102743 | The Enhancement of the Radio Load Information Interaction | ZTE | Not Treated |
R3‑102744 | The enhancement of the load information interaction procedure | ZTE | Noted |
R3‑102745 | The additional information for UL MLB | ZTE | Noted |
R3‑102746 | Discussion on energy saving enhancement | ZTE | Noted |
R3‑102747 | MRO enhancement for idle mode ping-pong problem | ZTE | Not Treated |
R3‑102748 | Cell reselection parameters negotiation | ZTE | Not Treated |
R3‑102749 | Proposed TS on ANR for UTRAN | ZTE | Revised |
R3‑102750 | Secondary Serving Cell Information | ZTE | Not Agreed |
R3‑102751 | Secondary Serving Cell Information | ZTE | Not Agreed |
R3‑102752 | Secondary Serving Cell Information | ZTE | Not Agreed |
R3‑102753 | HSUPA Independent Schedule for Cell Portion | ZTE | Withdrawn |
R3‑102754 | Introduction of HSUPA Schedule for Cell portion Indepented | ZTE | Withdrawn |
R3‑102755 | Introduction of HSUPA Schedule for Cell portion Indepented | ZTE | Withdrawn |
R3‑102756 | Introduction of HSUPA Schedule for Cell portion Indepented | ZTE | Withdrawn |
R3‑102757 | CR for Description of Energy Saving | CMCC, CATT | Not Agreed |
R3‑102758 | CR for Description of Energy Saving | CMCC, CATT | Revised |
R3‑102759 | Discussion on OAM architecture | CMCC | Noted |
R3‑102760 | CR for RN OAM architecture | CMCC | Not Treated |
R3‑102761 | Discussion on Issue about RN Confirmation | CMCC | Noted |
R3‑102762 | Discussion on Inter-RAT MRO Issue | CMCC | Not Treated |
R3‑102763 | Discussion on Further MLB Enhancement | CMCC | Noted |
R3‑102764 | CR for Further MLB Enhancement | CMCC | Noted |
R3‑102765 | TR update of Energy Saving for E-UTRAN | CMCC | Noted |
R3‑102766 | TP for Descriptions and Inter-eNB Energy Saving Scenarios and Solutions | CMCC | Revised |
R3‑102767 | Discussion on Signalling Connection for HNB to HNB Mobility | Huawei, Qualcomm Incorporated | Noted |
R3‑102768 | Clarification on the SCCP connection for intra-GW inter-HNB mobility | Huawei | Revised |
R3‑102769 | Performance analyze for soft handover between HNBs | Huawei | Noted |
R3‑102770 | LIPA SIPTO impact on termination of CN interface in RAN | Huawei | Noted |
R3‑102771 | Time Interval Definition in RLF Report | Samsung | Not Treated |
R3‑102772 | Overall flow for MRO evaluation in Rel-10 | Samsung | Not Treated |
R3‑102773 | Addition of eICIC information to LOAD INFORMATION message | Samsung | Revised |
R3‑102774 | X2 update for eICIC | Samsung | Not Available |
R3‑102775 | X2 Setup between GW and HeNB | Samsung | Not Treated |
R3‑102776 | Proposal for Inter-eNB energy saving mechanisms | Samsung | Not Available |
R3‑102777 | X2 Handover termination at the HeNB GW | Samsung, Alcatel-Lucent, CATT, CMCC | Not Treated |
R3‑102778 | X2 usage for HeNB mobility enhancement | Samsung, Motorola, ZTE, CATT, New Postcom, LG Electronics, InterDigital | Noted |
R3‑102779 | HeNB GW functionality to terminate X2 handover procedure | Samsung | Not Treated |
R3‑102780 | X2 HO routing and identification issue | Samsung | Not Treated |
R3‑102781 | LIPA Impact In RAN3 | Samsung | Not Treated |
R3‑102782 | LIPA Impact In RAN3 | Samsung | Not Treated |
R3‑102783 | RLF reporting in case of HO failure | Samsung | Not Treated |
R3‑102784 | Load exchange interval selection in Inter-RAT energy saving | TNO, Huawei | Revised |
R3‑102785 | Clarification for the X2 setup procedure | CATT | Noted |
R3‑102786 | Consideration on X2 setup for HeNB mobility enhancement | LG Electronics | Not Treated |
R3‑102787 | Introduction of MCE initiated SESSION START and SESSION STOP procedures | Orange SA | Revised |
R3‑102788 | LPPa Message Definition to Support UTDOA | TruePosition | Noted |
R3‑102789 | Aspects of CS fallback handling during HO | InterDigital | Withdrawn |
R3‑102790 | Configuration of Relay ECGI | InterDigital | Noted |
R3‑102791 | Aspects of Phased RN Startup | InterDigital | Not Treated |
R3‑102792 | Introduction of partial failure in Resource Status Reporting Initiation procedure | Alcatel-Lucent | Revised |
R3‑102793 | Benefits of event-triggered and multi-cell inter-RAT cell load reporting | Alcatel-Lucent | Noted |
R3‑102794 | Inter-RAT cell load reporting for multiple cells | Alcatel-Lucent | Not Treated |
R3‑102795 | Event-triggered inter-RAT cell load reporting | Alcatel-Lucent | Not Treated |
R3‑102796 | Cost/benefits of Rel-10 extension of RLF report for intra-LTE MRO | Alcatel-Lucent | Not Treated |
R3‑102797 | Handover optimisation using periodic UE measurements | Alcatel-Lucent | Not Treated |
R3‑102798 | Inter-RAT MRO: Too late HO and unnecessary HO | Alcatel-Lucent | Not Treated |
R3‑102799 | MDT impacts on S1 and X2 | Alcatel-Lucent | Noted |
R3‑102800 | MDT impacts on RANAP | Alcatel-Lucent | Noted |
R3‑102801 | Priority handling of MT calls from LTE into UMTS via eMPS using CSFB | AT&T | Noted |
R3‑102802 | Periodic Reporting for CellID Positioning Method and clarification of reporting of CellID measurements. | Polaris Wireless | Revised |
R3‑102803 | Inclusion of IMSI/IMEI in PCAP Discussion | Polaris Wireless | Postponed |
R3‑102804 | IRAT measurements for enhanced positioning capabilities Discussion | Polaris Wireless | Postponed |
R3‑102805 | Clarification to ANR Operation | Samsung, NEC | Revised |
R3‑102806 | Consideration on PDN-GW selection of the RN | Nokia Siemens Networks | Noted |
R3‑102807 | X2 TNL address discovery issues of the RN | Nokia Siemens Networks | Not Treated |
R3‑102808 | HO type determination | Nokia Siemens Networks | Noted |
R3‑102809 | RN neighbor discovery | Nokia Siemens Networks | Not Treated |
R3‑102810 | Discussion of Mobile Load Balancing for Relay | Nokia Siemens Networks | Not Treated |
R3‑102811 | Time information to be reported in the UE-originated RLF reporting in case of RRC connection setup | Nokia Siemens Networks | Not Treated |
R3‑102812 | [DRAFT] Request to enable UE-originated RLF reporting after fresh RRC connection setup | Nokia Siemens Networks | Not Treated |
R3‑102813 | Avoiding unnecessary handovers in inter-RAT environment | Nokia Siemens Networks | Noted |
R3‑102814 | Information needed to avoid unnecessary handovers in inter-RAT environment | Nokia Siemens Networks | Not Treated |
R3‑102815 | Additional information to be exchanged for intra-LTE UL MLB purposes | Nokia Siemens Networks, Vodafone | Noted |
R3‑102816 | Additional information to be exchanged for intra-LTE UL MLB purposes (stage-2) | Nokia Siemens Networks, Vodafone | Not Treated |
R3‑102817 | On TDM eICIC Coordination for Macro+Pico Cases | Nokia Siemens Networks | Not Treated |
R3‑102818 | Enhancement of the IP address exchange mechanism for ANR purposes | Nokia Siemens Networks, Deutsche Telekom | Revised |
R3‑102819 | Benefit of exchanging neighbor lists (NLs) between HNB and HNB-GW | Nokia Siemens Networks, Alcatel-Lucent | Noted |
R3‑102820 | Introduction of HNB GW transparent HNB to HNB mobility procedures using HNBAP | Nokia Siemens Networks | Revised |
R3‑102821 | Enhanced neighbor relationship establishment for HNB-to-HNB mobility based on HNBAP | Nokia Siemens Networks | Revised |
R3‑102822 | IuUP enhancements to support HNBAP based enhanced HNB to HNB mobility | Nokia Siemens Networks | Noted |
R3‑102823 | X2 mobility aspects with HeNB-GW proxy | Nokia Siemens Networks | Revised |
R3‑102824 | X2 mobility via HeNB GW proxy | Nokia Siemens Networks | Not Treated |
R3‑102825 | [DRAFT] Applicability of Handover restriction list for CSFB (To SA2, CT1, RAN2) | Nokia Siemens Networks | Revised |
R3‑102826 | Correction of missing presence statements in RAB Parameters tabular | Nokia Siemens Networks | Revised |
R3‑102827 | Scope of RAN3 work for Inter-RNS ANR | Nokia Siemens Networks | Noted |
R3‑102828 | Clarification of use of RNC Id | ip.access Ltd | Not Agreed |
R3‑102829 | Clarification of use of RNC Id | ip.access Ltd | Not Agreed |
R3‑102830 | Clarification of HNB De-registration procedure | Ip.access Ltd | Not Agreed |
R3‑102831 | Clarification of HNB De-registration procedure | Ip.access Ltd | Not Agreed |
R3‑102832 | Alignment of tabular with ASN.1 for S1 Setup message | Ip.access Ltd | Not Agreed |
R3‑102833 | Alignment of tabular with ASN.1 for S1 Setup message | Ip.access Ltd | Not Agreed |
R3‑102834 | SRVCC procedure in case of PS handover failure | NTT DOCOMO, INC. | Postponed |
R3‑102835 | Clarification on SRVCC procedure in case of PS handover failure | NTT DOCOMO, INC. | Revised |
R3‑102836 | [DRAFT] Reply LS on PS handover failure during the SRVCC (To: SA2; Cc: RAN2, GERAN2) | NTT DOCOMO, INC. | Postponed |
R3‑102837 | Support of CS only SRVCC handover to UTRAN with PS handover support | NTT DOCOMO, INC. | Postponed |
R3‑102838 | Applicable network architecture for X2 based HeNB mobility | NTT DOCOMO, INC. | Not Treated |
R3‑102839 | Use case of direct X2 based (H)eNB-HeNB mobility | NTT DOCOMO, INC. | Noted |
R3‑102840 | DeNB cell measurements during RN attach | NTT DOCOMO, INC. | Not Treated |
R3‑102841 | TA configuration for relays | NTT DOCOMO, INC., New Postcom, LG Electronics, Qualcomm Incorporated, Mitsubishi Electric, Alcatel-Lucent, NEC, Huawei, CMCC, CATT, KDDI, Telecom Italia | Noted |
R3‑102842 | Way forward on RN E-CGI configuration | NTT DOCOMO, INC., Fujitsu, Panasonic, KDDI, Motorola, Samsung, Alcatel-Lucent, Telecom Italia, ZTE, Qualcomm Incorporated, Orange, NEC | Noted |
R3‑102843 | Analysis on inter-RAT ping pong handover | NTT DOCOMO, INC., Ericsson | Noted |
R3‑102844 | Consideration on Too Early HO and HO Too Wrong Cell scenarios | NTT DOCOMO, INC. | Not Treated |
R3‑102845 | Offloading action based on redirection procedure | NTT DOCOMO, INC. | Noted |
R3‑102846 | Offloading action based on redirection procedure | NTT DOCOMO, INC. | Noted |
R3‑102847 | Prioritised handling of MPS session in S1-AP PAGING message | NTT DOCOMO, INC., KDDI | Revised |
R3‑102848 | Prioritised handling of IMS signalling in S1-AP PAGING message | NTT DOCOMO, INC., Huawei | Noted |
R3‑102849 | Prioritised handling of IMS signalling in S1-AP PAGING message | NTT DOCOMO, INC., Huawei | Noted |
R3‑102850 | [DRAFT] LS on prioritised handling of IMS signalling in S1-AP PAGING message | NTT DOCOMO, INC. | Not Treated |
R3‑102851 | Rel-10 enhancements for intra-LTE cell load reporting. | Kyocera Corp | Not Treated |
R3‑102852 | Rel-10 enhancements for intra-LTE cell load reporting. | Kyocera Corp | Not Treated |
R3‑102853 | Neighbour Discovery by a Relay Node | Mitsubishi Electric | Not Treated |
R3‑102854 | X2 Management with a HeNB-GW | Mitsubishi Electric | Not Treated |
R3‑102855 | Feasibility of Compensation-based intra-RAT Energy Saving | Mitsubishi Electric | Revised |
R3‑102856 | Mechanism for optimised cell wake up in hotspot deployments | Nokia Siemens Networks | Noted |
R3‑102857 | Negotiation-based algorithm for ES compensations | Nokia Siemens Networks | Noted |
R3‑102858 | Handling of CDMA2000 HO Required Indication | Alcatel-Lucent | Revised |
R3‑102859 | Correction of GBR and MBR definition | Alcatel-Lucent | Revised |
R3‑102860 | Introduction of MTC Overload Support | Alcatel-Lucent | Not Treated |
R3‑102861 | Introduction of MTC Overload Support | Alcatel-Lucent | Not Treated |
R3‑102862 | Handling Service-Based RAT restrictions and operator preferences | Alcatel-Lucent, AT&T, Orange, Vodafone | Revised |
R3‑102863 | Introduction of Service Handover | Alcatel-Lucent, AT&T, Orange, Vodafone | Revised |
R3‑102864 | Introduction of Service Handover | Alcatel-Lucent, AT&T, Orange, Vodafone | Revised |
R3‑102865 | Paging priority indication over S1 for eMPS | Alcatel-Lucent | Noted |
R3‑102866 | Paging priority indication over S1 for MPS | Alcatel-Lucent | Not Treated |
R3‑102867 | [DRAFT] LSout on Paging priority indication over S1 for eMPS | Alcatel-Lucent | Not Treated |
R3‑102868 | Introduction of LIPA function | Alcatel-Lucent | Revised |
R3‑102869 | Introduction of LIPA function | Alcatel-Lucent | Not Treated |
R3‑102870 | Introduction of LIPA function | Alcatel-Lucent | Not Treated |
R3‑102871 | Correction of semantics description | Ericsson | Noted |
R3‑102872 | Addtion of missing acronym definition | Ericsson | Agreed |
R3‑102873 | Analysis of potential RAN3 impacts from the Carrier Aggregation WI | Ericsson | Noted |
R3‑102874 | HeNB Mobility Enhancements Scenarios | Ericsson | Noted |
R3‑102875 | Addressing of HeNBs | Ericsson | Noted |
R3‑102876 | Static GW Selection for Relay Nodes | Ericsson | Noted |
R3‑102877 | Relay Node ECGI Configuration | Ericsson, Huawei, Nokia Siemens Networks | Revised |
R3‑102878 | DeNB Proxying of Inbound Non-UE Associated X2 Messages | Ericsson | Noted |
R3‑102879 | Correction of 4C-HSDPA secondary serving HS-DSCH RL change | Ericsson | Revised |
R3‑102880 | Secondary serving HS-DSCH RL change for 4C-HSDPA | Ericsson | Noted |
R3‑102881 | Correction of 4C-HSDPA secondary serving HS-DSCH RL change | Ericsson | Revised |
R3‑102882 | Inter-RAT MRO – Detection of too early inter-RAT handover with no RLF | Ericsson | Noted |
R3‑102883 | Considerations UE Counting | Ericsson | Not Treated |
R3‑102884 | Considerations about ARP and UE counting | Ericsson | Noted |
R3‑102885 | [DRAFT] LS on admission control using additional RAN specific information | Ericsson | Not Treated |
R3‑102886 | Requirements UE Counting | Ericsson | Noted |
R3‑102887 | Overload management for low priority accesses | Ericsson | Noted |
R3‑102888 | Enhancement of Overload management for low priority accesses | Ericsson | Not Treated |
R3‑102889 | The need for PLMN civic address location format | Ericsson | Noted |
R3‑102890 | Introduction of possibility to report Civic Address | Ericsson | Not Treated |
R3‑102891 | Introduction of possibility to report Civic Address | Ericsson | Not Treated |
R3‑102892 | Inconsistencies in Energy Saving Use Cases | Ericsson | Noted |
R3‑102893 | MDT overview | Ericsson | Noted |
R3‑102894 | Scenario for Inter-eNB Energy Saving Enhancement | CHTTL | Withdrawn |
R3‑102895 | Discussion on Inter-RAT Energy Saving | CHTTL | Withdrawn |
R3‑102896 | Requirement of Enhanced Inter-HeNB mobility | Alcatel-Lucent | Noted |
R3‑102897 | Optimized Solution for Enhanced inter-HeNB Mobility | Alcatel-Lucent | Not Treated |
R3‑102898 | Introduction for Enhanced inter-HeNB Mobility Architecture | Alcatel-Lucent | Not Treated |
R3‑102899 | Introduction of Enhanced inter-HeNB Mobility Function | Alcatel-Lucent | Not Treated |
R3‑102900 | Introduction of Enhanced inter-HeNB Mobility Procedures | Alcatel-Lucent | Not Treated |
R3‑102901 | Inbound Mobility to HeNB open cells | Alcatel-Lucent | Noted |
R3‑102902 | Inbound Mobility to HeNB open cells | Alcatel-Lucent | Not Treated |
R3‑102903 | Inbound Mobility to HeNB open cells | Alcatel-Lucent | Noted |
R3‑102904 | MBMS Status Report Solution over M2 interface | Alcatel-Lucent Shanghai Bell, Alcatel-Lucent | Noted |
R3‑102905 | Introduction of Status Report function over M2 interface | Alcatel-Lucent Shanghai Bell, Alcatel-Lucent | Not Treated |
R3‑102906 | Automatic PCI Selection at Relay Nodes | Qualcomm Incorporated, NTT DOCOMO, Inc. | Not Treated |
R3‑102907 | GW Selection for Relay | Qualcomm Incorporated | Noted |
R3‑102908 | GW selection for relays | Qualcomm Incorporated | Not Treated |
R3‑102909 | Un Bearer Management with Configurable Uu-Un Bearer Mapping | Qualcomm Incorporated | Not Treated |
R3‑102910 | HO type determination with relays | Qualcomm Incorporated | Noted |
R3‑102911 | Mobility Load Balancing in case of relay nodes | Qualcomm Incorporated | Not Treated |
R3‑102912 | Mobility Robustness Optimization for HeNB | Qualcomm Incorporated | Not Treated |
R3‑102913 | OAM requirements for configuraiton of ranges of HO parameters for MRO | Qualcomm Incorporated | Revised |
R3‑102914 | RIM-based Signaling in Inter-RAT Network Energy Saving | Qualcomm Incorporated | Noted |
R3‑102915 | LIPA impacts in RAN3 | Qualcomm Incorporated | Noted |
R3‑102916 | On using unicast bearer for MBMS | Qualcomm Incorporated | Revised |
R3‑102917 | O&M and addressing Requirements | Alcatel-Lucent | Noted |
R3‑102918 | P-GW function embedded in Denb and addressing requirements | Alcatel-Lucent, Qualcomm Incorporated | Revised |
R3‑102919 | Solution for P-GW selection in relay | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Noted |
R3‑102920 | Non UE associated S1 message handling in Relay system | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Noted |
R3‑102921 | Further consideration for intra-DeNB handover for RN | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Treated |
R3‑102922 | Configuration of E-CGI and radio parameters for Relay Operation | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Noted |
R3‑102923 | Choice of Handover Type by Relay Node | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Noted |
R3‑102924 | GTP handling for control plane messages | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | Not Treated |
R3‑102925 | HNBAP based management of U-RNTI for HNB to HNB Cell Fach mobility | Nokia Siemens Networks | Not Treated |
R3‑102926 | PPI value for SABP in Iuh | NEC | Revised |
R3‑102927 | Correction of E-RAB Data Forwarding in HANDOVER COMMAND and DOWNLINK S1 CDMA2000 TUNNELING | NEC, Motorola | Revised |
R3‑102928 | Optimized HNB to HNB mobility in Cell-DCH – HNB-GW based solution | NEC, Kineto Wireless, Huawei, Orange, Samsung, IP. Access, China Unicom, ZTE | Noted |
R3‑102929 | RANAP procedure clarification in the Optimized HNB to HNB mobility in Cell-DCH | NEC, Kineto Wireless, Huawei, Orange, Samsung, IP. Access, China Unicom, ZTE | Noted |
R3‑102930 | U-RNTI management over the Iuh interface | NEC, Kineto Wireless, Orange | Not Treated |
R3‑102931 | U-RNTI management over the Iuh interface: Comparison of Solutions | NEC | Not Treated |
R3‑102932 | U-RNTI Management over the Iuh interface | NEC, Kineto Wireless, Orange | Not Treated |
R3‑102933 | U-RNTI Management over the Iuh interface | NEC, Kineto Wireless, Orange | Not Treated |
R3‑102934 | Intra CSG Intra HNB-GW Mobility in CELL FACH state | NEC, Kineto Wireless, Orange | Not Treated |
R3‑102935 | Intra CSG Intra HNB-GW Mobility in CELL FACH state | NEC, Kineto Wireless, Orange | Not Treated |
R3‑102936 | Intra CSG Intra HNB-GW Mobility in CELL FACH state | NEC, Kineto Wireless, Orange | Not Treated |
R3‑102937 | Handling of MME Overload in a RN deployment | NEC | Noted |
R3‑102938 | Adding MMEC to Overload related messages | NEC | Not Treated |
R3‑102939 | On Rel-9 HNB-to-HNB mobility | Qualcomm Incorporated | Noted |
R3‑102940 | LS on How to differentiate RN and UE (Source: SA3; To: CT4; Cc: SA2, RAN2, RAN3) | SA3 | Noted |
R3‑102941 | Reply LS to LS on the security on the direct interface between H(e)NBs (Source: SA3; To: RAN3) | SA3 | Noted |
R3‑102942 | Reply LS on transfer of source eNB IP address via SON Configuration Transfer IE (Source: SA3; To: RAN3) | SA3 | Noted |
R3‑102943 | Response to R3-102913 | Huawei | Not Treated |
R3‑102944 | Response to R3-102772 | Alcatel-Lucent | Not Treated |
R3‑102945 | Response to R3-102915 | Alcatel-Lucent | Noted |
R3‑102946 | Response to R3-102817 | Qualcomm Incorporated | Not Available |
R3‑102947 | Response to R3-102897/102777 | NTT DOCOMO, INC. | Not Treated |
R3‑102948 | Response to R3-102815/102745 | NTT DOCOMO, INC. | Revised |
R3‑102949 | Response to R3-102931 (U-RNTI management over the Iuh interface: Comparison of Solutions) | Nokia Siemens Networks | Not Treated |
R3‑102950 | Response to R3-102625 | Ericsson | Not Treated |
R3‑102951 | Response to R3-102626 | Ericsson | Not Treated |
R3‑102952 | Response to R3-102627 | Ericsson | Not Treated |
R3‑102953 | Response to R3-102781 | Ericsson | Not Treated |
R3‑102954 | Response to R3-102782 | Ericsson | Not Treated |
R3‑102955 | Response to R3-102928 | Alcatel-Lucent | Noted |
R3‑102956 | Progress on relay node security (Source: SA3; To: RAN2, RAN3, CT1, CT4, CT6; Cc: SA2) | SA3 | Noted |
R3‑102957 | LS on OAM security and OAM connection issues of RN (Source: SA3; To: RAN3; Cc:SA2, SA5, RAN2) | SA3 | Noted |
R3‑102958 | LS reply on Location Information for MDT (Source: SA5; To: SA2, RAN2; Cc: RAN3, SA1) | SA5 | Noted |
R3‑102959 | Handling Service-Based RAT restrictions and operator preferences | Alcatel-Lucent, AT&T, Orange, Vodafone | Postponed |
R3‑102960 | Introduction of Service Handover | Alcatel-Lucent, AT&T, Orange, Vodafone | Not Treated |
R3‑102961 | Introduction of Service Handover | Alcatel-Lucent, AT&T, Orange, Vodafone | Not Treated |
R3‑102962 | Handling of CDMA2000 HO Required Indication | Alcatel-Lucent, KDDI | Agreed |
R3‑102963 | Feasibility of compensation based intra-RAT Energy Saving | Mitsubishi Electric | Noted |
R3‑102964 | Rejection of Connections towards a congested CN Node for UMTS and LTE | Vodafone | Noted |
R3‑102965 | Rejection of Connections towards a congested CN Node | Vodafone | Not Treated |
R3‑102966 | Enhanced registration procedure for supporting HNB to HNB mobility using HNBAP | Nokia Siemens Networks | Postponed |
R3‑102967 | Support of HNB GW transparent HNB to HNB mobility in HNBAP | Nokia Siemens Networks | Revised |
R3‑102968 | On using unicast bearer for MBMS | Qualcomm Incorporated | Noted |
R3‑102969 | Clarification on SRVCC procedure in case of PS handover failure | NTT DOCOMO, INC. | Revised |
R3‑102970 | [DRAFT] Reply LS on Consideration on counting for MBMS activation (To: RAN2; Cc: SA2) | Huawei | Revised |
R3‑102971 | Alignment of tabular with ASN.1 for S1 Setup message | Ip.access Ltd | Agreed |
R3‑102972 | [DRAFT] Applicability of Handover restriction list for CSFB (To: SA2, CT1, RAN2) | Nokia Siemens Networks | Revised |
R3‑102973 | CR for Description of Energy Saving | CMCC, CATT | Agreed |
R3‑102974 | [DRAFT] LS on GBR and MBR definition (To: SA2; Cc: RAN2) | Alcatel-Lucent | Revised |
R3‑102975 | Correction of E-RAB Data Forwarding in HANDOVER COMMAND and DOWNLINK S1 CDMA2000 TUNNELING | NEC, Motorola | Agreed |
R3‑102976 | Clarification for setting AP IDs in the Error Indication msg and incorrect causes | Motorola, KDDI | Revised |
R3‑102977 | Clarification for setting the AP IDs in Error Indication msg | Motorola, KDDI | Revised |
R3‑102978 | Correction of GBR and MBR definition | Alcatel-Lucent | Postponed |
R3‑102979 | PPI value for SABP in Iuh | NEC | Agreed |
R3‑102980 | Prioritised handling of MPS session in S1-AP PAGING message | NTT DOCOMO, INC., KDDI | Revised |
R3‑102981 | [DRAFT] LS on Paging Priority indication over S1 for eMPS (To: SA2; Cc: RAN2) | Alcatel-Lucent | Revised |
R3‑102982 | Enhancement of the IP address exchange mechanism for ANR purposes | Nokia Siemens Networks, Deutsche Telekom | Postponed |
R3‑102983 | Reply LS on MBR to be greater than GBR for MBMS services (Source: SA2; To: RAN3; Cc: RAN2) | SA2 | Noted |
R3‑102984 | Clarification on definition of MMEC | Huawei | Noted |
R3‑102985 | Introduction of MC-HSUPA to RNSAP | CATT | Postponed |
R3‑102986 | Introduction of MC-HSUPA to NBAP | CATT | Postponed |
R3‑102987 | Introduction of MU-MIMO to RNSAP | CATT | Not Treated |
R3‑102988 | Introduction of MU-MIMO to NBAP | CATT | Not Treated |
R3‑102989 | Addition of HNB-GW Status procedure. | Alcatel-Lucent | Noted |
R3‑102990 | Correction of missing presence statements in RAB Parameters tabular | Nokia Siemens Networks | Not Available |
R3‑102991 | Correction of 4C-HSDPA secondary serving HS-DSCH RL change | Ericsson | Agreed |
R3‑102992 | Correction of 4C-HSDPA secondary serving HS-DSCH RL change | Ericsson | Agreed |
R3‑102993 | Proposed skeleton TS for UTRAN ANR | ZTE | Revised |
R3‑102994 | [DRAFT] LS on UTRAN ANR TS (To: RAN2) | ZTE | Revised |
R3‑102995 | Introduction of MC-HSUPA for 1.28Mcps TDD | TD Tech | Postponed |
R3‑102996 | Relay Node ECGI Configuration | Ericsson, Huawei, Nokia Siemens Networks, CATT | Noted |
R3‑102997 | [DRAFT] LS on SIPTO at Iu-PS work progress in RAN (To: SA2) | Huawei | Revised |
R3‑102998 | eNB Configuration Update procedure in RN startup and detach procedure | Huawei, NTT DOCOMO, INC. Ericsson, CMCC, New Postcom | Revised |
R3‑102999 | S1 non UE associated msg handling | Huawei | Agreed |
R3‑103000 | X2 mobility aspects with HeNB-GW proxy | Nokia Siemens Networks | Not Treated |
R3‑103001 | Active mode Inter RAT Ping-Pong | Huawei | Noted |
R3‑103002 | Clarify the criteria for S1 HO and X2 HO related to Relay | Motorola, New Postcom, CATT | Not Available |
R3‑103003 | [Introduction of HNB GW transparent HNB to HNB mobility procedures using HNBAP] | Nokia Siemens Networks | Revised |
R3‑103004 | [Enhanced neighbor relationship establishment for HNB-to-HNB mobility based on HNBAP] | Nokia Siemens Networks | Revised |
R3‑103005 | Stage 2 for the X2 based mobility enhancement between HeNBs | Qualcomm Incorporated, NTT DOCOMO, Ericsson, Hitachi, Inter Digital, NEC, Vodafone, Samsung, Alcatel-Lucent, KDDI, ETRI, Motorola, Nokia Siemens Networks, LG Electronics, CATT | Noted |
R3‑103006 | [DRAFT] Response LS on the security on the direct interface between H(e)NBs (To: SA3) | Alcatel-Lucent | Revised |
R3‑103007 | Addition of eICIC information to LOAD INFORMATION message | Samsung, KDDI | Not Treated |
R3‑103008 | Introduction of MCE initiated SESSION START and SESSION STOP procedures | Orange SA | Noted |
R3‑103009 | Addition of HNB-GW Status procedure | Alcatel-Lucent, ip.access | Noted |
R3‑103010 | [DRAFT] LS on Clarification for Iu Flex usage with MTC devices (To: SA2; Cc: RAN2) | Huawei | Revised |
R3‑103011 | Clarification on SRVCC procedure in case of PS handover failure | NTT DOCOMO, INC. | Postponed |
R3‑103012 | [DRAFT] Reply LS on PS handover failure during the SRVCC (To: SA2; Cc: RAN2, GERAN2) | NTT DOCOMO, INC. | Not Treated |
R3‑103013 | [DRAFT] LS on PS handover failure during SRVCC from UTRAN (HSPA) to UTRAN (To: RAN2; Cc: SA2, GERAN2) | NTT DOCOMO, INC. | Not Available |
R3‑103014 | [DRAFT] LS on Clarification for Iu Flex usage with MTC devices (To: SA2; Cc: RAN2) | Huawei | Agreed |
R3‑103015 | LS on Clarification for Iu Flex usage with MTC devices (To: SA2; Cc: RAN2) | RAN3 | Approved |
R3‑103016 | [DRAFT] Reply LS on GERAN and UTRAN handling of RFSP Index/SPID (To: CT4, SA2; Cc: GERAN2, CT1) | Telecom Italia | Revised |
R3‑103017 | Periodic Reporting for CellID Positioning Method and clarify of reporting of CellID measurements. | Polaris Wireless, AT&T, T-Mobile USA, Thales Alenia, TruePosition | Postponed |
R3‑103018 | Correct name in E-RAB Release procedure and add NAS may be piggybacked | Motorola, KDDI | Withdrawn |
R3‑103019 | Incorrect causes in the Error Indication msg | Motorola, KDDI | Noted |
R3‑103020 | Clarification for setting the AP IDs in Error Indication msg | Motorola, KDDI | Withdrawn |
R3‑103021 | [DRAFT] LS on Clarification for Cell_FACH mobility of CSG UEs (To: RAN2) | Huawei | Revised |
R3‑103022 | Introduction of MCE initiated MBMS Session Start Request | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei, Orange SA | Revised |
R3‑103023 | [DRAFT] Reply LS on Consideration on counting for MBMS activation (To: RAN2; Cc: SA2) | Huawei | Revised |
R3‑103024 | Proposed skeleton TS for UTRAN ANR | ZTE | Noted |
R3‑103025 | [DRAFT] LS on UTRAN ANR TS (To: RAN2) | ZTE | Agreed |
R3‑103026 | Introduction of HNB to HNB mobility procedure using direct interface | Alcatel-Lucent, Huawei | Postponed |
R3‑103027 | Text Proposal for HRNSAP | Alcatel-Lucent | Postponed |
R3‑103028 | [DRAFT] LS on Clarification for Cell_FACH mobility of CSG UEs (To: RAN2) | Huawei | Agreed |
R3‑103029 | LS on Clarification for Cell_FACH mobility of CSG UEs (To: RAN2) | RAN3 | Approved |
R3‑103030 | Clarification on Handover Restriction List | Huawei, Nokia Siemens Networks, NTT DoCoMo, INC. | Revised |
R3‑103031 | Clarification on Handover Restriction List | Huawei, Nokia Siemens Networks, NTT DoCoMo, INC. | Revised |
R3‑103032 | Reply LS on Clarification for Iu Flex usage with MTC devices (Source: SA2; To: RAN3; Cc: CT4, RAN2) | SA2 | Noted |
R3‑103033 | MBMS Session Report | Vice Chairman | Noted |
R3‑103034 | Intra-LTE MRO evolution | Alcatel-Lucent | Not Treated |
R3‑103035 | TP for TR 3.023 | Alcatel-Lucent | Not Treated |
R3‑103036 | Analysis of Rel9 MRO | Huawei | Revised |
R3‑103037 | Response to R3-102815/102745 | NTT DOCOMO, INC., KDDI | Noted |
R3‑103038 | Way forward for RLF reporting in Rel-10 | Samsung | Noted |
R3‑103039 | P-GW function embedded in Denb and addressing requirements | Alcatel-Lucent, Qualcomm Incorporated | Revised |
R3‑103040 | [DRAFT] LS on LIPO deactivation issue (To: SA2) | Alcatel-Lucent | Revised |
R3‑103041 | Introduction of LIPA function | Alcatel-Lucent | Not Treated |
R3‑103042 | Analysis of Rel9 MRO | Huawei, Alcatel-Lucent, Nokia Siemens Networks, Samsung | Noted |
R3‑103043 | Clarification of use of RNC-ID | ip.access Ltd | Agreed |
R3‑103044 | Introduction of TOF as a logical node | Huawei | Revised |
R3‑103045 | Introduction of TOF as a logical node | Huawei | Not Treated |
R3‑103046 | Introduction of TOF as a logical node | Huawei | Not Treated |
R3‑103047 | HSPA Session Report | Vice Chairman | Noted |
R3‑103048 | OAM requirements for configuration of ranges of HO parameters for MRO | Qualcomm Incorporated, Telecom Italia, Orange | Withdrawn |
R3‑103049 | Optimized HNB to HNB mobility in Cell-DCH – HNB-GW based solution | NEC, Kineto Wireless, Huawei, Orange, Samsung, IP. Access, China Unicom, ZTE | Not Available |
R3‑103050 | Call Flow to Support UTDOA | TruePosition | Noted |
R3‑103051 | OAM requirements for configuration of ranges of HO parameters for MRO | Qualcomm Incorporated, Telecom Italia, Orange | Not Treated |
R3‑103052 | Clarification on the SCCP connection for intra-GW inter-HNB mobility | Huawei, Qualcomm Incorporated | Revised |
R3‑103053 | TP for Descriptions and Inter-eNB Energy Saving Scenarios and Solutions | CMCC | Noted |
R3‑103054 | [DRAFT] LS on OAM issues of RN initial attachment (To: SA3; Cc: SA5) | CMCC | Noted |
R3‑103055 | LS on time-domain extension of Rel 8/9 backhaul-based ICIC for Macro-Pico scenario (Source: RAN1; To: RAN2, RAN3, RAN4) | RAN1 | Noted |
R3‑103056 | Clarification to ANR Operation | Samsung, NEC, NTT DOCOMO Inc., New Postcom, LG Electronics, Qualcomm Incorporated, CMCC, Mitsubishi Electric, ZTE, KDDI, Alcatel-Lucent | Revised |
R3‑103057 | Initial thought on RAN3 impact from eICIC | Qualcomm Incorporated, Ericsson, Nokia Siemens Networks, Samsung, AT&T, NTT DoCoMo, KDDI, InterDigital | Revised |
R3‑103058 | Reply LS to S2-104432 on Release 10 NIMTC Conclusions (to:SA1, SA2, CT1; cc: RAN3, GERAN2; contact: Ericsson) | RAN2 | Noted |
R3‑103059 | Stage-2 TP for UTRAN ANR | ZTE, China Unicom, NEC, China Mobile, Alcatel-Lucent, Qualcomm Incorporated, CATT, Orange, Vodafone, Telecom Italia | Not Available |
R3‑103060 | Initial thought on RAN3 impact from eICIC | Qualcomm Incorporated, Ericsson, Nokia Siemens Networks, Samsung, AT&T, NTT DoCoMo, KDDI, InterDigital, CMCC | Noted |
R3‑103061 | Relay discussion paper | Motorola | Not Available |
R3‑103062 | Clarification on Handover Restriction List | Huawei, Nokia Siemens Networks, NTT DoCoMo, INC. | Agreed |
R3‑103063 | Clarification on Handover Restriction List | Huawei, Nokia Siemens Networks, NTT DoCoMo, INC. | Agreed |
R3‑103064 | [DRAFT] Applicability of Handover restriction list for CSFB (To: SA2, CT1, RAN2) | Nokia Siemens Networks | Revised |
R3‑103065 | Introduction of TOF as a logical node | Huawei | Not Treated |
R3‑103066 | [DRAFT] LS on GBR and MBR definition (To: SA2; Cc: RAN2) | Alcatel-Lucent | Revised |
R3‑103067 | [DRAFT] Reply LS on GERAN and UTRAN handling of RFSP Index/SPID (To: CT4, SA2; Cc: GERAN2, CT1) | Telecom Italia | Agreed |
R3‑103068 | Reply LS on GERAN and UTRAN handling of RFSP Index/SPID (To: CT4, SA2; Cc: GERAN2, CT1) | RAN3 | Approved |
R3‑103069 | [Stage-2 TP for HNB mobility using HNBAP] | Nokia Siemens Networks | Not Available |
R3‑103070 | [Stage-3 TP for HNB mobility using HNBAP] | Nokia Siemens Networks | Not Available |
R3‑103071 | LS on UTRAN ANR TS (To: RAN2) | RAN3 | Approved |
R3‑103072 | Load exchange interval selection in Inter-RAT energy saving | TNO, Huawei, CMCC, Alcatel-Lucent | Noted |
R3‑103073 | TR for Energy saving agreements | CMCC | Revised |
R3‑103074 | Introduction of TOF as a logical node | Alcatel-Lucent | Not Treated |
R3‑103075 | Introduction of TOF as a logical node | Alcatel-Lucent | Not Treated |
R3‑103076 | [DRAFT] LS on RN E-GCI Configuration by O&M (To: SA5) | Alcatel-Lucent | Revised |
R3‑103077 | Introduction of partial failure in Resource Status Reporting Initiation procedure | Alcatel-Lucent | Postponed |
R3‑103078 | Clarification on Inbound Mobility to HNB | Huawei, Qualcomm Incorporated | Agreed |
R3‑103079 | Introduction of MCE initiated MBMS Session Start Request | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, Huawei, Orange SA | Agreed |
R3‑103080 | [DRAFT] LS on RN S/P GW selection during startup procedure (To: SA2) | Huawei | Revised |
R3‑103081 | Stage-2 updates to RN initial attachment | Huawei, Ericsson, New Postcom, CMCC | Revised |
R3‑103082 | Report of offline discussion on relay stage 2 issues | NTT DOCOMO, INC. | Noted |
R3‑103083 | [DRAFT] LS on UL Mobility Load Balancing utilising UL TPC parameters (To: RAN1) | NTT DOCOMO, INC. | Agreed |
R3‑103084 | Simple solution for Too late handover | Alcatel-Lucent | Not Treated |
R3‑103085 | [DRAFT] Response LS on the security on the direct interface between H(e)NBs (To: SA3) | Alcatel-Lucent | Agreed |
R3‑103086 | Introduction of the SIPTO at Iu-PS Function | Huawei | Noted |
R3‑103087 | Introduction of the SIPTO at Iu-PS Function | Huawei | Not Treated |
R3‑103088 | Introduction of the SIPTO at Iu-PS Function | Huawei | Not Treated |
R3‑103089 | Clarification to ANR Operation | Samsung, NEC, NTT DOCOMO Inc., New Postcom, LG Electronics, Qualcomm Incorporated, CMCC, Mitsubishi Electric, ZTE, KDDI, Alcatel-Lucent | Agreed |
R3‑103090 | [DRAFT] LS on RN E-GCI Configuration by O&M (To: SA5; Cc: RAN2) | Alcatel-Lucent | Agreed |
R3‑103091 | LS on RN E-GCI Configuration by O&M (To: SA5; Cc: RAN2) | RAN3 | Approved |
R3‑103092 | [DRAFT] LS on RN S/P GW selection during startup procedure (To: SA2) | Huawei | Agreed |
R3‑103093 | LS on RN S/P GW selection during startup procedure (To: SA2) | RAN3 | Approved |
R3‑103094 | Stage-2 updates to RN initial attachment | Huawei, Ericsson, New Postcom, CMCC | Revised |
R3‑103095 | P-GW function embedded in Denb and addressing requirements | Alcatel-Lucent, Qualcomm Incorporated | Agreed |
R3‑103096 | - | - | - |
R3‑103097 | Handling of multiple RLF indications | Huawei | Noted |
R3‑103098 | Prioritised handling of MPS session in S1-AP PAGING message | NTT DOCOMO, INC., KDDI | Revised |
R3‑103099 | [DRAFT] LS on SIPTO at Iu-PS work progress in RAN (To: SA2) | Huawei | Not Treated |
R3‑103100 | [DRAFT] LS on Paging Priority indication over S1 for eMPS (To: SA2; Cc: RAN2) | Alcatel-Lucent | Agreed |
R3‑103101 | LS on Paging Priority indication over S1 for eMPS (To: SA2; Cc: RAN2) | RAN3 | Revised |
R3‑103102 | Way forward for RLF reporting in Rel-10 | Samsung, Nokia Siemens Networks, Ericsson, Huawei, CATT | Noted |
R3‑103103 | [DRAFT] Request to enable UE-originated RLF reporting after fresh RRC connection setup (To: RAN2) | Nokia Siemens Networks, Samsung, Ericsson, Huawei, CATT | Postponed |
R3‑103104 | [DRAFT] Reply LS on Consideration on counting for MBMS activation (To: RAN2; Cc: SA2) | Huawei | Agreed |
R3‑103105 | LS on UL Mobility Load Balancing utilising UL TPC parameters (To: RAN1) | RAN3 | Approved |
R3‑103106 | TR for Energy saving agreements | CMCC | Noted |
R3‑103107 | [DRAFT] Applicability of Handover restriction list for CSFB (To: SA2, CT1, RAN2) | Nokia Siemens Networks | Agreed |
R3‑103108 | Applicability of Handover restriction list for CSFB (To: SA2, CT1, RAN2) | Nokia Siemens Networks | Revised |
R3‑103109 | [DRAFT] LS on GBR and MBR definition (To: SA2; Cc: CT1, RAN2) | Alcatel-Lucent | Agreed |
R3‑103110 | LS on GBR and MBR definition (To: SA2; Cc: CT1, RAN2) | RAN3 | Approved |
R3‑103111 | Response LS on the security on the direct interface between H(e)NBs (To: SA3) | RAN3 | Approved |
R3‑103112 | Stage-2 updates to RN initial attachment | Huawei, Ericsson, New Postcom, CMCC | Agreed |
R3‑103113 | Reply LS on Consideration on counting for MBMS activation (To: RAN2; Cc: SA2) | RAN3 | Approved |
R3‑103114 | LS on LIPA deactivation issue (To: SA2) | Alcatel-Lucent | Approved |
R3‑103115 | Applicability of Handover restriction list for CSFB (To: SA2, CT1, RAN2) | RAN3 | Approved |
R3‑103116 | Prioritised handling of MPS session in S1-AP PAGING message | NTT DOCOMO, INC., KDDI | Agreed |
R3‑103117 | LS on Paging Priority indication over S1 for eMPS (To: SA2; Cc: RAN2) | RAN3 | Approved |
page generated from database: 2024-03-25 09:25:51