3GPP TDocs (written contributions) at meeting
Meeting: R3-59 - 2008-02-11 to 2008-02-15, Sorrento
meeting id: R3-59 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
R3‑080001 | Agenda RAN3#59, Sorrento, Italy 11 - 15 February 2008 | Chairman | - |
R3‑080002 | Revised draft report of RAN3#58, Jeju Island, Korea | MCC | - |
R3‑080003 | Workplan and Working Procedures v0.28.1 (Rel-7) | MCC | - |
R3‑080004 | LS to SA2 on LS on “subscriber type” indication via S1 (R2-075458 Source: TSG RAN WG2, To: TSG SA WG2, Cc: TSG RAN WG3) | TSG RAN WG2 | - |
R3‑080005 | Reply LS to LS on data forwarding discussion at RAN3#57bis (R2-075461 Source: TSG RAN WG2, To: TSG RAN WG3, Cc: ) | TSG RAN WG2 | reply to R3-072018 |
R3‑080006 | LS on ”Principles on Idle Mode Signalling Reduction” (R2-075462 Source: TSG RAN WG2, To: TSG SA WG2, Cc: CT1,CT4,TSG RAN WG3) | TSG RAN WG2 | response to S2-073938=R3-071972 |
R3‑080007 | LS to SA2 on need for Priority and PBR signaling as part of the QoS information (R2-075465 Source: TSG RAN WG2, To: TSG SA WG2, Cc: TSG RAN WG3) | TSG RAN WG2 | - |
R3‑080008 | LS on RACH power control optimisation use case (R2-075463 Source: TSG RAN WG2, To: TSG RAN WG1, Cc: TSG RAN WG3,TSG RAN WG4) | TSG RAN WG2 | - |
R3‑080009 | LS on RACH optimisation use case (R2-075464 Source: TSG RAN WG2, To: TSG RAN WG3,TSG SA WG5, Cc: ) | TSG RAN WG2 | - |
R3‑080010 | Response LS Automatic Neighbour Relation Function (R4-072193 Source: TSG RAN WG4, To: TSG RAN WG3,TSG SA WG5,TSG RAN WG2, Cc: ) | TSG RAN WG4 | reply to R3-072014 |
R3‑080011 | Reply LS (C4-071868/R3-072019) Transfer of PDCP SDU Sequence Numbers over X2 Interface (C4-071892 Source: CT WG4, To: TSG RAN WG3, Cc: TSG RAN WG2,TSG SA WG2) | CT WG4 | reply to R3-072019 |
R3‑080012 | Reply to LS on Stage 2 Documentation Principles for SAE Specifications (C4-072034_Reply_LS_stage2-stage3_params Source: TSG CT WG4, To: TSG SA WG2,CT1,CT3,TSG RAN WG2,TSG RAN WG3,TSG GERAN WG2,TSG SA WG5, Cc: ) | TSG CT WG4 | reply to S2-073894=R3-071785 |
R3‑080013 | LS on detection of duplicated NAS message during Inter-eNB Intra-LTE Handover (C1-073191 LS on dup NAS msg at inter-eNB HO Source: CT1, To: TSG RAN WG3, Cc: TSG RAN WG2) | CT1 | reply to R3-072025 |
R3‑080014 | Response to LS on Physical-layer Cell Identity Collision (R1-075099 Source: TSG RAN WG1, To: TSG RAN WG3, Cc: TSG RAN WG2,TSG SA WG5) | TSG RAN WG1 | reply to R3-072016 |
R3‑080015 | Reply LS on CSG Cells Handling (R2-075456 Source: TSG RAN WG2, To: TSG CT WG1, Cc: TSG SA WG2,TSG RAN WG3,TSG CT WG6) | TSG RAN WG2 | reply to C1-072709=R3-072068 |
R3‑080016 | Reply to LS on NAS handling during intra-LTE handover (R2-075457 Source: TSG RAN WG2, To: TSG RAN WG3,TSG CT WG1, Cc: ) | TSG RAN WG2 | reply to R3-072025 |
R3‑080017 | Reply LS on Registration in Densely-populated area – clarification on some technical issues (R2-075419 Source: TSG RAN WG2, To: TSG SA WG2, Cc: TSG GERAN,CT1,TSG RAN WG3) | TSG RAN WG2 | - |
R3‑080018 | Response LS to SA3 on HomeNodeB authorization / localisation (R4-072152 Source: TSG RAN WG4, To: TSG SA WG3, Cc: TSG RAN WG3,TSG RAN WG2,TSG GERAN,TSG SA WG1,TSG SA WG2,TSG SA WG5) | TSG RAN WG4 | reply to S3-070834=R3-071990 |
R3‑080019 | Response to LS on signalling for paging (S2-075795 Source: TSG SA WG2, To: TSG RAN WG2 SA 3, Cc: TSG RAN WG3,CT WG1) | TSG SA WG2 | R2-074587=S2-074591=R3-072064 |
R3‑080020 | Reply LS on IP Fragmentation (S2-075831_Draft Reply LS on IP Fragmentation Source: TSG SA WG2, To: TSG CT WG4, Cc: TSG CT WG1,TSG RAN WG2,TSG RAN WG3) | TSG SA WG2 | reply to C4-071576=R3-072071 |
R3‑080021 | Reply LS on Home NodeB/eNodeB regarding localization/authorization (S2-075833_Draft Reply LS on Home eNodeB Source: TSG SA WG2, To: TSG RAN WG4,TSG SA WG3, Cc: TSG SA WG1,TSG RAN WG2,TSG RAN WG3,TSG GERAN) | TSG SA WG2 | R4-071516=R3-071783 and S3-070834=R3-071990 |
R3‑080022 | draft LS on GNSS Satellites Identification in UMTS System Information (GP-071980 Source: TSG GERAN WG2, To: TSG RAN,TSG RAN WG2, Cc: TSG RAN WG3) | TSG GERAN WG2 | R2-075471 |
R3‑080023 | Response to LS on feasibility of using RLF recovery to aid neighbour discovery (GP-072012 Source: TSG GERAN, To: TSG RAN WG2,TSG RAN WG3, Cc: TSG SA WG5) | TSG GERAN | - |
R3‑080024 | LS on GAN Iu mode (GP-072032 Source: TSG GERAN, To: TSG RAN WG2,TSG RAN WG3, Cc: TSG RAN) | TSG GERAN | - |
R3‑080025 | Response to RAN2 LS on SFN Reading from the Target Cell at HO (R2-074590) (R1-075108 Source: TSG RAN WG1, To: TSG RAN WG2,TSG RAN WG3, Cc: TSG RAN WG4) | TSG RAN WG1 | reply to R2-074590=R3-072059 |
R3‑080026 | Reply LS on piggy-backed Service Request (S2-075871_email_approved_S2-075598 Source: TSG SA WG2, To: TSG RAN WG2, Cc: TSG SA WG3,TSG CT WG1,TSG RAN WG3) | TSG SA WG2 | reply to S3-070388, C1-071993, R2-074573 and R3-072026 |
R3‑080027 | LS on EPS Identities (S2-075872_e-mail_approved_S2-075650 Source: TSG SA WG2, To: TSG RAN WG2,TSG RAN WG3,CT WG1,CT WG4,TSG SA WG3, Cc: TSG SA WG1) | TSG SA WG2 | - |
R3‑080028 | LS on Earthquake and Tsunami Warning System (S2-075874_email_approved_S2-075812_ETWS_LS Source: TSG SA WG2, To: TSG RAN WG2,TSG RAN WG3,TSG GERAN WG2,CT1,TSG SA WG1,TSG SA WG3, Cc: ) | TSG SA WG2 | - |
R3‑080029 | Response LS on EPS Mobility Management (EMM) sublayer state machine in UE (S2-075875_e-mail_approved_S2-075838 Source: TSG SA WG2, To: CT1,TSG RAN WG2,TSG RAN WG3, Cc: ) | TSG SA WG2 | reply to C1-072537=R3-072070 |
R3‑080030 | TAU in Connected Mode (S2-075870_e-mail_rev9_S2-075834 LS on TAU_rev9 Source: TSG SA WG2, To: TSG RAN WG2,TSG RAN WG3,CT1, Cc: ) | TSG SA WG2 | - |
R3‑080031 | LS on Iur backward compatiblility with E-PCH (R2-075420 Source: TSG RAN WG2, To: TSG RAN WG3, Cc: None.) | TSG RAN WG2 | - |
R3‑080032 | LS on CSG related mobility (stage2 text) (R2-075478 Source: TSG RAN WG2, To: TSG SA WG1,TSG RAN WG4,TSG GERAN, Cc: TSG RAN WG3,TSG SA WG2,CT1,TSG SA WG3) | TSG RAN WG2 | - |
R3‑080033 | LS reply on availability of IMSI and IMEI(SV) in eNB (S5-080229r1 Source: TSG SA WG5, To: TSG RAN WG3, Cc: TSG SA WG3) | TSG SA WG5 | reply to R3-072003 |
R3‑080034 | LS on the use of HS-DPCCH (R2-080579 Source: TSG RAN WG2, To: TSG RAN WG1,TSG RAN WG3, Cc: ) | TSG RAN WG2 | - |
R3‑080035 | LS on UE release indication from SRNC to NodeB (R1-080609 Source: TSG RAN WG1, To: TSG RAN WG3, Cc: TSG RAN WG2) | TSG RAN WG1 | - |
R3‑080036 | Reply to LS on various aspects related to GERAN to E-UTRAN interworking (R1-080610 Source: TSG RAN WG1, To: TSG GERAN, Cc: TSG RAN WG2,TSG RAN WG3,TSG RAN WG4,TSG RAN) | TSG RAN WG1 | - |
R3‑080037 | Reply to RAN2 LS on RACH Power Control Optimisation Use case (R1-080612 Source: TSG RAN WG1, To: TSG RAN WG2, Cc: TSG RAN WG3,TSG RAN WG4) | TSG RAN WG1 | reply to R2-075463=R3-080008 |
R3‑080038 | Reply LS on Load balancing (R1-080617 Source: TSG RAN WG1, To: TSG RAN WG2,TSG RAN WG3, Cc: ) | TSG RAN WG1 | reply to R3-072444 |
R3‑080039 | LS on the progress made on Enhanced Uplink in CELL_FACH State in FDD (R1-080618 Source: TSG RAN WG1, To: TSG RAN WG2,TSG RAN WG3, Cc: ) | TSG RAN WG1 | - |
R3‑080040 | LS on QoS Parameters via S1 (S2-080913 Source: TSG SA WG2, To: TSG RAN WG2, Cc: TSG RAN WG3) | TSG SA WG2 | reply to R2-075465=R3-080007 |
R3‑080041 | Reply LS on mechanism to support reordering in target eNB (S2-080961-LS-reordering-support.1 Source: TSG SA WG2, To: TSG RAN WG3,CT4, Cc: ) | TSG SA WG2 | reply to R3-072409 |
R3‑080042 | Reply LS Request for clarification and feedback on switching of the UL Tunnel Endpoint at X2 Handover (S2-080963-LS-X2-SGW-reloc.1 Source: TSG SA WG2, To: TSG RAN WG3, Cc: ) | TSG SA WG2 | reply to R3-072413 |
R3‑080043 | Reply-LS on “subscriber type” indication via S1 (S2-080965-LS-to-RAN2-on-Subscriber-Type-on-S1 Source: TSG SA WG2, To: TSG RAN WG2, Cc: TSG RAN WG3) | TSG SA WG2 | reply to R2-075458=R3-080004 |
R3‑080044 | LS on inter-MME load balancing, Attach/TAU/Service Request procedures and corresponding RRC/S1 connection establishment procedures (S2-080991 Source: TSG SA WG2, To: TSG RAN WG2,TSG RAN WG3,CT 1, Cc: TSG SA WG3) | TSG SA WG2 | - |
R3‑080045 | Reply on Reply LS on Area and Access Restrictions (S2-080995 Source: TSG SA WG2, To: TSG RAN WG3, Cc: CT 1,TSG RAN WG2) | TSG SA WG2 | reply to R3-072395 |
R3‑080046 | LS on Enhanced Uplink for CELL_FACH in FDD (R2-080575 Source: TSG RAN WG2, To: TSG RAN WG1,TSG RAN WG3, Cc: ) | TSG RAN WG2 | - |
R3‑080047 | Reply LS on outstanding NAS messages (R2-080601 Source: TSG RAN WG2, To: TSG SA WG3, Cc: TSG RAN WG3,TSG SA WG2,CT1) | TSG RAN WG2 | - |
R3‑080048 | LS on applicability of “subscriber type” indication for UTRAN & GERAN networks (R2-080605 Source: TSG RAN WG2, To: TSG SA WG2,TSG RAN WG3,TSG GERAN, Cc: ) | TSG RAN WG2 | - |
R3‑080049 | Reply LS on UE Inactivity for UE historical information (R2-080615 Source: TSG RAN WG2, To: TSG RAN WG3, Cc: ) | TSG RAN WG2 | reply to R3-072011 |
R3‑080050 | Reply on LS on Area and Access Restrictions (R2-080616 Source: TSG RAN WG2, To: TSG RAN WG3,TSG SA WG2, Cc: CT1) | TSG RAN WG2 | reply to R3-072395 |
R3‑080051 | LS on Paging Repetition (R2-080617 Source: TSG RAN WG2, To: TSG SA WG2,TSG CT1, Cc: TSG RAN WG3) | TSG RAN WG2 | reply to R3-072414 |
R3‑080052 | Reply LS on piggy-backed Service Request (R2-080620 Source: TSG RAN WG2, To: TSG SA WG2, Cc: TSG SA WG3,TSG CT WG1,TSG RAN WG3) | TSG RAN WG2 | reply to S2-075871=R3-080026 |
R3‑080053 | LS on outstanding NAS messages (S3a071035-v2 Source: TSG SA WG3, To: TSG RAN WG2,TSG RAN WG3,TSG SA WG2,CT1, Cc: ) | TSG SA WG3 | - |
R3‑080054 | Reply LS to ”Reply LS on Active mode key change” (S3a071046 Source: TSG SA WG3, To: TSG RAN WG3, Cc: TSG RAN WG2) | TSG SA WG3 | replaced by R3-080136 |
R3‑080055 | Status Report: Enhancements for SRNS Relocation Procedure | Nokia Siemens Networks | - |
R3‑080056 | Status Report: Enhancements for FDD HSPA Evolution | Nokia Siemens Networks | - |
R3‑080057 | LS on MBMS Improvements in HSPA Architecture (S2-081006_MBMS in HSPA_LS to RAN3 Source: TSG SA WG2, To: TSG RAN WG3, Cc: ) | TSG SA WG2 | - |
R3‑080058 | Location Reporting procedure | NTT DoCoMo Inc. | - |
R3‑080059 | RAN performance monitoring | NTT DoCoMo Inc. | - |
R3‑080060 | Clarification of Home eNB scenarios and definition in RAN3 | NTT DoCoMo Inc. | - |
R3‑080061 | Support of text-based broadcast messages | NTT DoCoMo Inc. | - |
R3‑080062 | EUTRAN Proxy in support of massive deployment of HNBs | Mitsubishi Electric | - |
R3‑080063 | Optional MME routing information in INITIAL UE MESSAGE | Mitsubishi Electric | not treated |
R3‑080064 | Dynamic Setup of HNBs | Mitsubishi Electric | - |
R3‑080065 | HNB Location Certification | Mitsubishi Electric | - |
R3‑080066 | LS on Ran1 ICIC status (R1 080564_LS ICIC x ran3 Source: TSG RAN WG1, To: TSG RAN WG3, Cc: TSG RAN WG2) | Telecom Italia | - |
R3‑080067 | Half Duplex FDD Operation in LTE (R1-080614 Source: TSG RAN WG1, To: TSG RAN WG2,TSG RAN WG3,TSG RAN WG4,TSG RAN WG5, Cc: ) | TSG RAN WG1 | - |
R3‑080068 | RLF-based neighbour list optimization | Qualcomm Europe | - |
R3‑080069 | UTRAN enhancements for the support of inter-cell interference cancellation | Qualcomm Europe | - |
R3‑080070 | E-DCH Resource Release in CELL_FACH | Qualcomm Europe | - |
R3‑080071 | AMBR for S1 | ZTE | - |
R3‑080072 | AMBR for X2 | ZTE | - |
R3‑080073 | Trace deactivation | ZTE | - |
R3‑080074 | Trace deactivation | ZTE | - |
R3‑080075 | Add Cause in Reset Request | ZTE | - |
R3‑080076 | Add Cell Type in Served Cell Information | ZTE | - |
R3‑080077 | Generation of Neighbour Relations | ZTE | - |
R3‑080078 | Introduce MME id into S1 Setup Response | ZTE | - |
R3‑080079 | Proposed Text for E-MBMS architecture in 36.401 | ZTE | - |
R3‑080080 | Consideration on MBSFN Border cell type | ZTE | - |
R3‑080081 | 36.444: Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M3 Application Protocol (M3AP) | ZTE | - |
R3‑080082 | Capacity and coverage SON use case | Alcatel-Lucent | - |
R3‑080083 | List of open issues for TS36.410 | Alcatel-Lucent | - |
R3‑080084 | Dedication of common streams over S1-MME | Alcatel-Lucent | - |
R3‑080085 | Dedication of common streams over X2 | Alcatel-Lucent | - |
R3‑080086 | Data link layer proposal | Alcatel-Lucent | - |
R3‑080087 | Introduction of HFN Reference | Alcatel-Lucent | - |
R3‑080088 | UL Forwarding Selective retransmission | Alcatel-Lucent | - |
R3‑080089 | UL Forwarding Selective retransmission | Alcatel-Lucent | - |
R3‑080090 | Selective forwarding for completion of S1 based handover | Alcatel-Lucent | - |
R3‑080091 | Interaction with the SAE bearers to be released | Alcatel-Lucent | - |
R3‑080092 | Overspecification of the bearer type | Alcatel-Lucent | - |
R3‑080093 | UE Context Release over S1 and IOT issues | Alcatel-Lucent | - |
R3‑080094 | UE Context Release over S1 and IOT issues | Alcatel-Lucent | - |
R3‑080095 | Correction of S1 setup and Reset | Alcatel-Lucent | - |
R3‑080096 | Correction of S1 setup and Reset | Alcatel-Lucent | - |
R3‑080097 | Correction DL forwarding | Alcatel-Lucent | for further updates. Could be covered already |
R3‑080098 | Completion of TX2relocoverall | Alcatel-Lucent, Nortel | - |
R3‑080099 | Timing of X2 Setup | Alcatel-Lucent | - |
R3‑080100 | Handover Cancellation procedure for S1 and X2 handover | NTT DoCoMo, Inc. | - |
R3‑080101 | Location Reporting procedure on S1 | NTT DoCoMo, Inc. | - |
R3‑080102 | Impact of inter eNB handover on Location Reporting procedure | NTT DoCoMo, Inc. | - |
R3‑080103 | List of issues for 36.412 and 36.422 | NTT DoCoMo, Inc. | - |
R3‑080104 | SCTP related issues | NTT DoCoMo, Inc. | - |
R3‑080105 | GAN variant of Iu-based 3G HNB Architecture | Kineto Wireless Inc., NEC, Motorola | - |
R3‑080106 | Rapporteur Update for 36.414 | Nortel | - |
R3‑080107 | Editorial correction on 36.414 | Nortel | - |
R3‑080108 | Rapporteur Update for 36.414 | Nortel | - |
R3‑080109 | Editorial correction on 36.424 | Nortel | - |
R3‑080110 | Benefit of multiple SCTP associations | Nortel | - |
R3‑080111 | Text proposal for S1 Multiple SCTP association | Nortel | not treated |
R3‑080112 | Text proposal for X2 Multiple SCTP associations | Nortel | not treated |
R3‑080113 | Node Id and Node Name usage | Nortel | - |
R3‑080114 | S1 Setup Ids correction | Nortel | - |
R3‑080115 | Abnormal Condition for S1 Setup | Nortel | - |
R3‑080116 | Abnormal condition for S1 Setup: Multiple association reject | Nortel | - |
R3‑080117 | Abnormal condition for X2 Setup: Multiple association reject | Nortel | - |
R3‑080118 | The Message Structure IE is Strike Back | Nortel | - |
R3‑080119 | Return of the Message Structure IE | Nortel | - |
R3‑080120 | Initial Context Setup Response NAS PDU alignment | Nortel | - |
R3‑080121 | PRB-based approach for non-GBR bearers | Nortel | - |
R3‑080122 | S1 Overload discussion | Nortel | - |
R3‑080123 | Adding IMSI in Paging | NEC | - |
R3‑080124 | The value range of IEs in 36.413 | NEC | - |
R3‑080125 | The value range of IEs in 36.413 | NEC | not treated |
R3‑080126 | The discussion and proposal on the S1 Setup procedure and X2 Setup procedure | NEC | - |
R3‑080127 | Correction to the S1 Setup procedure | NEC | - |
R3‑080128 | Correction to the X2 Setup procedure | NEC | withdrawn, replaced by R3-080346 |
R3‑080129 | The need of MME ID in Handover Request in 36.423 | NEC | - |
R3‑080130 | Description of MME identity in 36.401 | NEC | - |
R3‑080131 | MME ID in X2 Handover Request | NEC | agreed for big CR |
R3‑080132 | Transport Address description in 36.401 | NEC | - |
R3‑080133 | Transport Address description in 36.401 | NEC | agreed for big CR |
R3‑080134 | Description of Mobility Management in 36.401 | NEC | - |
R3‑080135 | Description of Mobility Management in 36.401 | NEC | - |
R3‑080136 | Reply LS to ”Reply LS on Active mode key change” (S3a071057 Source: TSG SA WG3, To: TSG RAN WG3, Cc: TSG RAN WG2) | TSG SA WG3 | reply to R3-072410 |
R3‑080137 | Configuration Rule for solving Enhanced Cell FACH Iur Backward Compatibility Problem in NW using RNC ID Extension Scheme | Nokia Siemens Networks, Nokia | 25.999 |
R3‑080138 | Introduction of new Configuration Rule for Extended RNC ID Scheme | Nokia Siemens Networks, Nokia | 25.999 |
R3‑080139 | Correction on MAC-d PDU Size for E-DCH | Nokia Siemens Networks, Nokia | - |
R3‑080140 | Correction on MAC-d PDU Size for E-DCH | Nokia Siemens Networks, Nokia | - |
R3‑080141 | Correction on MAC-d PDU Size for E-DCH | Nokia Siemens Networks, Nokia | - |
R3‑080142 | Correction on Abnormal Condition for identical cell on HSDPA/E-DCH Serving Cell | Nokia Siemens Networks, Nokia | - |
R3‑080143 | Correction on Abnormal Condition for identical cell on HSDPA/E-DCH Serving Cell | Nokia Siemens Networks, Nokia | - |
R3‑080144 | Correction on Abnormal Condition for identical cell on HSDPA/E-DCH Serving Cell | Nokia Siemens Networks, Nokia | - |
R3‑080145 | Correction on HS-DSCH MAC-d PDU Size Format IE in HS-DSCH Information to Modify | Nokia Siemens Networks, Nokia | - |
R3‑080146 | Correction on HS-DSCH MAC-d PDU Size Format IE in HS-DSCH Information to Modify | Nokia Siemens Networks, Nokia | - |
R3‑080147 | Correction on HS-DSCH MAC-d PDU Size Format IE in HS-DSCH Information to Modify | Nokia Siemens Networks, Nokia | - |
R3‑080148 | Abnormal Condition on DL L2 Improvement | Nokia Siemens Networks, Nokia | - |
R3‑080149 | Abnormal Condition on DL L2 Improvement | Nokia Siemens Networks, Nokia | - |
R3‑080150 | Abnormal Condition on DL L2 Improvement | Nokia Siemens Networks, Nokia | - |
R3‑080151 | X2 Load Information | Nokia Siemens Networks, Nokia | - |
R3‑080152 | FFS removal from 36.423 | Nokia Siemens Networks, Nokia | - |
R3‑080153 | FFS removal from 36.423 | Nokia Siemens Networks, Nokia | - |
R3‑080154 | R3.020 v0.40 | Nokia Siemens Networks, Nokia | - |
R3‑080155 | HeNBs S1 simplification by means of HeNB GW | Nokia Siemens Networks, Nokia | 36.300 |
R3‑080156 | Impacts on S1 from HeNB GW concept | Nokia Siemens Networks, Nokia | - |
R3‑080157 | Impacts on S1 from HeNB GW concept | Nokia Siemens Networks, Nokia | - |
R3‑080158 | Various E-MBMS Issues | Nokia Siemens Networks, Nokia | - |
R3‑080159 | MBMS session control related functions and procedures in E-UTRAN architecture | Nokia Siemens Networks, Nokia | - |
R3‑080160 | Comparison of the SYNC-protocol proposals | Nokia Siemens Networks, Nokia | 36.300 |
R3‑080161 | Security key update function on the S1 interface | Nokia Siemens Networks, Nokia | - |
R3‑080162 | Security key update function on the S1 interface | Nokia Siemens Networks, Nokia | 36.300 |
R3‑080163 | Security key update function on the S1 interface | Nokia Siemens Networks, Nokia | - |
R3‑080164 | MME initiated UE Context Release | Nokia Siemens Networks, Nokia | - |
R3‑080165 | MME initiated UE Context Release | Nokia Siemens Networks, Nokia | 36.300 |
R3‑080166 | MME initiated UE Context Release | Nokia Siemens Networks, Nokia | - |
R3‑080167 | UE capability info provision | Nokia Siemens Networks, Nokia | - |
R3‑080168 | UE capability info provision | Nokia Siemens Networks, Nokia | - |
R3‑080169 | NAS PDU IE in Initial Context Setup response message | Nokia Siemens Networks, Nokia | - |
R3‑080170 | NAS PDU IE in Initial Context Setup response message | Nokia Siemens Networks, Nokia | - |
R3‑080171 | Support of early DL data | Nokia Siemens Networks, Nokia | - |
R3‑080172 | System behaviour if last/default SAE bearer is released | Nokia Siemens Networks, Nokia | - |
R3‑080173 | Bearer lists in HO messages | Nokia Siemens Networks, Nokia | - |
R3‑080174 | Bearer lists in HO messages | Nokia Siemens Networks, Nokia | - |
R3‑080175 | EPS Identifiers | Nokia Siemens Networks, Nokia | - |
R3‑080176 | EPS Identifiers | Nokia Siemens Networks, Nokia | - |
R3‑080177 | S1 CDMA2000 Tunneling Procedure | Nokia Siemens Networks, Nokia,ricsson, Alcatel-Lucent, Motorola, Nortel, Verizon | - |
R3‑080178 | Signalling of Paging DRX value | Nokia Siemens Networks, Nokia | - |
R3‑080179 | Signalling of eNB Security capabilities | Nokia Siemens Networks, Nokia | - |
R3‑080180 | Signalling of eNB Security capabilities | Nokia Siemens Networks, Nokia | - |
R3‑080181 | Paging Identifiers | Nokia Siemens Networks, Nokia | - |
R3‑080182 | Load Balancing for the S1 Interface | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑080183 | Load Balancing for S1 Interface | Nokia Siemens Networks, Nokia, Vodafone | 36.300 |
R3‑080184 | Load Balancing concept for the S1 Interface stage 3 details | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑080185 | Load Balancing for the S1 Interface | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑080186 | Overload Handling for the S1 Interface | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑080187 | Overload Handling for S1 Interface | Nokia Siemens Networks, Nokia, Vodafone | 36.300 |
R3‑080188 | Overload Handling for the S1 Interface stage 3 details | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑080189 | Overload Handling for the S1 Interface | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑080190 | Adding 'Cause' and Cause Value for X2 Handover Request | Nokia Siemens Networks, Nokia | - |
R3‑080191 | Adding 'Cause' and Cause Value for X2 Handover Request | Nokia Siemens Networks, Nokia | - |
R3‑080192 | Adding HFN to X2 SN Status Transfer | Nokia Siemens Networks, Nokia | - |
R3‑080193 | Adding HFN to X2 SN Status Transfer | Nokia Siemens Networks, Nokia | - |
R3‑080194 | Signalling of MME Address in X2 Setup | Nokia Siemens Networks, Nokia | - |
R3‑080195 | Signalling of MME Address in X2 Setup | Nokia Siemens Networks, Nokia | - |
R3‑080196 | X2 Information Update | Nokia Siemens Networks, Nokia | - |
R3‑080197 | X2 Information Update | Nokia Siemens Networks, Nokia | - |
R3‑080198 | M1 Skeleton | Nokia Siemens Networks, Nokia | - |
R3‑080199 | M2 Skeleton | Nokia Siemens Networks, Nokia | - |
R3‑080200 | Iu Release+ Alternative for Enhanced Relocation | Nokia Siemens Networks, Nokia, Huawei | R3.021 |
R3‑080201 | Data Forwarding Scheme for Enhanced Relocation | Nokia Siemens Networks, Nokia | R3.021 |
R3‑080202 | NAS Handling for Enhanced Relocation | Nokia Siemens Networks, Nokia | R3.021, Relocation Commit ffs, NAS PDU SN open |
R3‑080203 | Direct Tunneling for Enhanced Relocation | Nokia Siemens Networks, Nokia | R3.021, include TEID parameter in Gn interface communication |
R3‑080204 | On Interworking with legacy CN | Nokia Siemens Networks, Nokia | R3.021 |
R3‑080205 | Current MBMS Service over flat architecture | Nokia Siemens Networks, Nokia | R3.022 |
R3‑080206 | Proposal for MBMS Improvement over flat architecture | Nokia Siemens Networks, Nokia | R3.022 |
R3‑080207 | Template for Evaluation Table for MBMS improvement | Nokia Siemens Networks, Nokia | R3.022 |
R3‑080208 | Functional Split for Enhanced UL in Cell FACH | Nokia Siemens Networks, Nokia | - |
R3‑080209 | Functional Split for Enhanced UL in Cell FACH | Nokia Siemens Networks, Nokia | - |
R3‑080210 | Solution for mapping between HS-DSCH RNTI and E-RNTI | Nokia Siemens Networks, Nokia | - |
R3‑080211 | Introduction of the Improved L2 in the uplink | Nokia Siemens Networks, Nokia | - |
R3‑080212 | 3G Home NodeB Architecture for Efficient Traffic Handling | Nokia Siemens Networks, Nokia Angelo | 25.820 |
R3‑080213 | E-DCH RL Set ID IE handling | Alcatel-Lucent | - |
R3‑080214 | E-DCH RL Set ID IE handling | Alcatel-Lucent | - |
R3‑080215 | Transport bearer replacement during HS-DSCH Modification | Alcatel-Lucent | - |
R3‑080216 | Transport bearer replacement during HS-DSCH Modification | Alcatel-Lucent | - |
R3‑080217 | Transport bearer replacement during HS-DSCH Modification | Alcatel-Lucent | - |
R3‑080218 | Transport bearer replacement during HS-DSCH Modification | Alcatel-Lucent | - |
R3‑080219 | UL DPCCH Slot Format 5 undefined | Alcatel-Lucent | - |
R3‑080220 | UL DPCCH Slot Format 5 undefined | Alcatel-Lucent | - |
R3‑080221 | Introduction of UMTS 700 MHz (Bands XII XIV) in 25.461 | Alcatel-Lucent | - |
R3‑080222 | Introduction of UMTS 700 MHz (Bands XII XIV) in 25.466 | Alcatel-Lucent | - |
R3‑080223 | 3G Home Node B | Alcatel-Lucent | - |
R3‑080224 | Coordination of MCEs by the EPC using Resource Refer-ences | Alcatel-Lucent | - |
R3‑080225 | Synchronization issue for E-MBMS signaling | Alcatel-Lucent | - |
R3‑080226 | Open Issues on resource allocation and multiplexing | Alcatel-Lucent | - |
R3‑080227 | List of Topics Issues for 36.420 | Alcatel-Lucent | - |
R3‑080228 | Skeleton for 36.440 | Alcatel-Lucent | - |
R3‑080229 | EUL power control gap for 1.28Mcps TDD | TD Tech Ltd. | - |
R3‑080230 | EUL power control gap for 1.28Mcps TDD | TD Tech Ltd. | - |
R3‑080231 | Enable node synchronization is supported by the user plane protocols for HS-DSCH | Huawei | - |
R3‑080232 | Enable node synchronization is supported by the user plane protocols for HS-DSCH | Huawei | can be re-allocated for REL-8 |
R3‑080233 | Enable node synchronization is supported by the user plane protocols for HS-DSCH | Huawei | can be re-allocated for REL-8 |
R3‑080234 | Enable node synchronization is supported by the user plane protocols for HS-DSCH | Huawei | can be re-allocated for REL-8 |
R3‑080235 | Enable node synchronization is supported by the user plane protocols for HS-DSCH | Huawei | can be re-allocated for REL-8 |
R3‑080236 | Enable node synchronization is supported by the user plane protocols for HS-DSCH | Huawei | can be re-allocated for REL-8 |
R3‑080237 | Enable node synchronization is supported by the user plane protocols for HS-DSCH | Huawei | can be re-allocated for REL-8 |
R3‑080238 | Addition of IE "Continuous Packet Connectivity HS-SCCH less Deactive Indicator" | Huawei | - |
R3‑080239 | Addition of IE "Continuous Packet Connectivity HS-SCCH less Deactive Indicator" | Huawei | - |
R3‑080240 | Changes to the format of TMGI | Huawei | ask CT4 for the impact |
R3‑080241 | Changes to the format of TMGI | Huawei | ask CT4 for the impact |
R3‑080242 | Way Forward on CS Call Establishment Improvement | Huawei | - |
R3‑080243 | Session Update Procedure in LTE MBMS | Huawei | - |
R3‑080244 | Consideration of E-MBMS service multiplexing order | Huawei | - |
R3‑080245 | Minimizing packet loss during MBMS transmission | Huawei | - |
R3‑080246 | Mapping Service area to MBSFA cell and Single cell | Huawei | - |
R3‑080247 | MBMS Service Continuity in E-UTRAN | Huawei | - |
R3‑080248 | Security information transfer in Handover procedure | Huawei | - |
R3‑080249 | UE Context Modification procedure | Huawei | - |
R3‑080250 | UE context modification procedure | Huawei | - |
R3‑080251 | Interface issue in centric MBMS architecture | Huawei | - |
R3‑080252 | Principles of evaluation of MBMS architecture over HSPA+ | Huawei | - |
R3‑080253 | MBMS over HSPA+ | Huawei | - |
R3‑080254 | Home eNB attachment scenario | Orange | - |
R3‑080255 | Load information exchange for the load balancing use case | Orange | - |
R3‑080256 | The NAS message in the SAE bearer release procedure | CATT | - |
R3‑080257 | The UE identity in the paging message | CATT | - |
R3‑080258 | Introduction of UE Context Release procedure | CATT | - |
R3‑080259 | Modification of S1 AP functions | CATT | - |
R3‑080260 | Modification of X2 AP functions | CATT | - |
R3‑080261 | Supporting multi-frequency operation on MBMS for 1.28Mcps TDD | CMCC, RITT, CATT,TD Tech, ZTE, Spreadtrum Communic | - |
R3‑080262 | Clarification of E-DCH non-scheduled Grant Information for 1.28Mcps TDD | CATT, TD-TECH, ZTE | - |
R3‑080263 | Clarification of E-DCH non-scheduled Grant Information for 1.28Mcps TDD | CATT, TD-TECH, ZTE | - |
R3‑080264 | Introduction of an additional UE Category for 1.28Mcps TDD E-DCH | CATT, TD-TECH, ZTE | - |
R3‑080265 | Introduction of an additional UE Category for 1.28Mcps TDD E-DCH | CATT, TD-TECH, ZTE | - |
R3‑080266 | Introduction of multi-frequency operation for HSUPA for 1.28Mcps TDD | CMCC, RITT, CATT,TD Tech, ZTE, Spreadtrum Communic | - |
R3‑080267 | Introduction of multi-frequency operation for HSUPA for 1.28Mcps TDD | CMCC, RITT, CATT,TD Tech, ZTE, Spreadtrum Communic | category? |
R3‑080268 | X2 interface for HNB | Samsung | - |
R3‑080269 | S1 connectivity for home Node B | Samsung | - |
R3‑080270 | E-MBMS service continuity | Samsung | - |
R3‑080271 | Change the definition of cell identity | Samsung | - |
R3‑080272 | Change the definition of cell identity | Samsung | - |
R3‑080273 | Correction of Cell Identitier | Samsung | - |
R3‑080274 | S1 handover | Samsung | - |
R3‑080275 | Multiple PDNs support and AMBR update | Samsung | - |
R3‑080276 | Multiple PDNs support and AMBR update | Samsung | - |
R3‑080277 | SAE Bearer Management Optimisation | Samsung | - |
R3‑080278 | SAE Bearer management procedure optimisation | Samsung | - |
R3‑080279 | NAS Non Delivery Indication trigger update | Samsung | - |
R3‑080280 | NAS Non Delivery Indication trigger update | Samsung | - |
R3‑080281 | Transfer of UE Radio Access Capability through S1 | Samsung | - |
R3‑080282 | Transfer of UE radio capability information through S1 | Samsung | - |
R3‑080283 | UE history information deletion | Samsung | wait for RAN2 |
R3‑080284 | 3G HNB Architecture | Samsung | - |
R3‑080285 | RFL Recovery Information over X2 | Nortel, Nokia Siemens Networks | - |
R3‑080286 | Reset Resource dedicated procedure | Nortel | - |
R3‑080287 | Reset Resource for S1 | Nortel | - |
R3‑080288 | Reset Resource for X2 | Nortel | - |
R3‑080289 | ASN.1 Compacted List IE | Nortel | - |
R3‑080290 | Addition of new causes for consistency | Nortel, Alcatel-Lucent | not treated |
R3‑080291 | Correction of mistake in CR1243 and other similar wording mistakes | Ericsson | - |
R3‑080292 | Event C and D for Received Scheduled E-DCH Power Share for Cell Portion | Ericsson | - |
R3‑080293 | Correction of Flexible PDU size modify | Ericsson | - |
R3‑080294 | Correction of Flexible PDU size modify | Ericsson | - |
R3‑080295 | Introduction of automatic neighbour relation function | Ericsson | 36.300 |
R3‑080296 | Inter-RAT/Frequency Automatic Neighbor Relation Measurements | Ericsson | replaced by R3-080420 |
R3‑080297 | S1 and X2 procedure and message names | Ericsson | - |
R3‑080298 | Finalisation of X2 Release Resource behaviour | Ericsson | - |
R3‑080299 | Definition of logical synchronisation port for phase- and time-synchronisation | Ericsson | - |
R3‑080300 | Definition of logical synchronisation port for phase- and time-synchronisation | Ericsson | - |
R3‑080301 | Area restriction in Shared networks | Ericsson | - |
R3‑080302 | Correction of Trace Depth IE | Ericsson | - |
R3‑080303 | Correction of Trace Depth IE | Ericsson | - |
R3‑080304 | Correction of Trace Reference IE | Ericsson | - |
R3‑080305 | Correction of Trace Reference IE | Ericsson | - |
R3‑080306 | TAI Clean up | Ericsson | - |
R3‑080307 | TAI Clean up | Ericsson | - |
R3‑080308 | Quality of Service corrections | Ericsson | - |
R3‑080309 | Addition of MME-Initiated S1 UE Context Release to S1AP | Ericsson | - |
R3‑080310 | Transfering UE Capability Information on S1 | Ericsson | - |
R3‑080311 | Text Proposal: Switching the UL Tunnel Endpoint in the Path Switch Request procedure | Ericsson | SA2 action on disordering to be studied |
R3‑080312 | Abnormal condition of Reset procedure | Ericsson | - |
R3‑080313 | Introducing MMEC to S1 SETUP RESPONSE | Ericsson | - |
R3‑080314 | Introduction of reset of parts of the S1 Interface | Ericsson | - |
R3‑080315 | S1 application data update | Ericsson | - |
R3‑080316 | S1 application data update | Ericsson | - |
R3‑080317 | S1 Flex Load balancing | Ericsson | - |
R3‑080318 | Capacity factor for S1 flex load balancing | Ericsson | - |
R3‑080319 | Additon of explicit TRACE START message | Ericsson | 36.300 |
R3‑080320 | Additon of explicit TRACE START message | Ericsson | - |
R3‑080321 | Additon of explicit TRACE START message | Ericsson | - |
R3‑080322 | Correction of ASN.1 inconsistencies | Ericsson | - |
R3‑080323 | Modifications of non technical nature in X2AP | Ericsson | agreed for big CR |
R3‑080324 | ASN.1 corrections | Ericsson | agreed for big CR |
R3‑080325 | Alignments to the client-server principle | Ericsson | - |
R3‑080326 | Alignment of the procedure text to the Client-Server principle | Ericsson | - |
R3‑080327 | Criticality corrections | Ericsson | agreed for big CR |
R3‑080328 | UL PDCP SN handling and maintaining Hyper Frame Number | Ericsson | - |
R3‑080329 | UL PDCP SN handling | Ericsson | 36.300 |
R3‑080330 | UL PDCP SN handling | Ericsson | - |
R3‑080331 | Maintaining Hyper Frame Number at handover | Ericsson | - |
R3‑080332 | Introduction of reset of parts of the X2 Interface | Ericsson | - |
R3‑080333 | More access restriction information | Ericsson | - |
R3‑080334 | Abnormal condition of Reset procedure | Ericsson | - |
R3‑080335 | Alignment of X2 Release Resource name to S1 naming | Ericsson | 36.300 |
R3‑080336 | Alignment of X2 Release Resource name to S1 naming | Ericsson | - |
R3‑080337 | SCTP PPI values for S1 and X2 (and Iub) | Ericsson | - |
R3‑080338 | Introduction of Improved L2 for Uplink | Ericsson | - |
R3‑080339 | Introduction of Improved L2 for Uplink | Ericsson | - |
R3‑080340 | Introduction of Improved L2 for Uplink | Ericsson | - |
R3‑080341 | Introduction of DOB for MBSFN operation | Ericsson | - |
R3‑080342 | Introduction of DOB for MBSFN operation | Ericsson | - |
R3‑080343 | Indication of UE 3GPP Relase to NodeB | Ericsson | to be continued offline |
R3‑080344 | Indication of UE 3GPP Relase to NodeB | Ericsson | to be continued offline |
R3‑080345 | Inclusion of Cell Id into common measurement report | Vodafone, Nokia Siemens Networks, Nokia, T-Mobile | - |
R3‑080346 | Correction to the X2 Setup procedure | NEC | - |
R3‑080347 | EUTRAN topology and MME selection for Home eNodeB | Huawei | - |
R3‑080348 | IPSec and NA(P)T for Home eNB | Huawei | - |
R3‑080349 | Pre-operational procedures of Home eNB | Huawei | - |
R3‑080350 | S1 Performance and Capacity Requirements for MME and LTE HNB | Huawei | - |
R3‑080351 | Discussion on 3G HNB Architecture | Huawei | - |
R3‑080352 | Downlink Detection Functionality for HNB | Huawei | - |
R3‑080353 | Consideration on Paging of 3G HNB | Huawei | - |
R3‑080354 | Resource Coordination between MCE and eNodeB at Session Start | Huawei | - |
R3‑080355 | Architecture for self-optimization | Huawei, China Mobile,Telecom Italia | - |
R3‑080356 | Alignment of SON Use Cases for Optimization | Huawei | - |
R3‑080357 | Mobility Robustness Optimization Use Case | Huawei | - |
R3‑080358 | Mobility Robustness Optimization Solution | Huawei | - |
R3‑080359 | Mobility Robustness Optimization | Huawei | 36.300 |
R3‑080360 | Mobility Load Balancing Optimization Use Case | Huawei,Telecom Italia | - |
R3‑080361 | Mobility Load Balancing Optimization Solution | Huawei,Telecom Italia | - |
R3‑080362 | Mobility Load Balancing Optimization | Huawei,Telecom Italia | 36.300 |
R3‑080363 | Coverage And Capacity Optimization Use Case | Huawei | - |
R3‑080364 | Capacity and Coverage Optimization Solution | Huawei | - |
R3‑080365 | Automatic Neighbor Relation function | Huawei | - |
R3‑080366 | Automatic Neighbor Relation function | Huawei | 36.300 |
R3‑080367 | MBMS session start procedure | Panasonic, Nokia Siemens Networks | - |
R3‑080368 | Consideration on mobility procedure from MC-PTM to SC-PTM | Panasonic | - |
R3‑080369 | MME overload indication | Panasonic | - |
R3‑080370 | 36. 445 Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M1 data transport (draft V0.0.0) | Panasonic | - |
R3‑080371 | TP on UDP/IP for M1 data transport | Panasonic | - |
R3‑080372 | TP on Diffserv code point marking for M1 data transport | Panasonic | - |
R3‑080373 | Home eNodeB mobility call flows | Nokia Siemens Networks, Nokia | - |
R3‑080374 | Alignment of S1 and X2 HO wrt UE behaviour | Nokia Siemens Networks, Nokia | - |
R3‑080375 | Alignment of S1 and X2 HO wrt UE behaviour | Nokia Siemens Networks, Nokia | - |
R3‑080376 | SON Use Case: Cell Phy_ID Automated Configuration | Nokia Siemens Networks, Nokia | - |
R3‑080377 | E-UTRAN Cell Identification | Nokia Siemens Networks, Nokia | - |
R3‑080378 | Downlink Load Balancing for ICIC | Nokia Siemens Networks, Nokia | - |
R3‑080379 | E-UTRAN MBMS procedures for broadcast mode (R3-072024 re-submission) | Nokia Siemens Networks, Nokia | agreed for 36.300 |
R3‑080380 | Impacts of RRC GANSS changes | Alcatel-Lucent, Thales | email checking until Wednesday20 Feb |
R3‑080381 | Handling End Marker Packet in E-UTRAN | Fujitsu | 36.300 |
R3‑080382 | LTE Stage 2 handling end marker packets | Fujitsu | 36.300 |
R3‑080383 | SCTP Association Initiation over X2 Interface | Fujitsu | - |
R3‑080384 | UE Measurement Bandwidth for Intra/Inter Frequency Measurements | NEC | 36.300/36.423 |
R3‑080385 | Ping pong detection during idle mode | NEC | 36.300 |
R3‑080386 | Addition of Reset Resource functionality in the Reset procedure | NEC | 36.413 |
R3‑080387 | Global Node id and |SCTP protocol | NEC | 36.413, 36.423 |
R3‑080388 | Details on Load Balancing and ICIC Signaling Mechanism | NEC | 36.423 |
R3‑080389 | Details on Load Balancing and ICIC Signaling Mechanism | NEC | - |
R3‑080390 | Handover preparation for handover to CDMA2000 HRPD | Nokia Siemens Networks | - |
R3‑080391 | Enhancements for FDD HSPA Evolution | Telecom Italia, Huawei | - |
R3‑080392 | UE context modification procedure | Huawei | 36.300 |
R3‑080393 | Load balancing scheme and X2 message support | Motorola | - |
R3‑080394 | Mechanism for MME overload notification | Motorola | - |
R3‑080395 | High Availability for eNB to MME Connectivity | Motorola | - |
R3‑080396 | Draft Reply LS on Signalling of additional spectrum emission requirements | Motorola | - |
R3‑080397 | Summary of HeNB definition email discussion | Motorola | - |
R3‑080398 | UL and DL ICIC indication | Nokia Siemens Networks | - |
R3‑080399 | UL and DL ICIC indication | Nokia Siemens Networks | - |
R3‑080400 | Load Balancing on X2 | Nokia Siemens Networks | - |
R3‑080401 | MME Address in HO Request | Nokia Siemens Networks, Nokia | - |
R3‑080402 | MME Address in HO Request | Nokia Siemens Networks, Nokia | - |
R3‑080403 | LS on Improved L2 for uplink (R2-080562 Source: TSG RAN WG2, To: TSG RAN WG3, Cc: ) | TSG RAN WG2 | - |
R3‑080404 | Load Balancing on X2 | Nokia Siemens Networks | - |
R3‑080405 | Subscriber Type in R8 3G & LTE | Vodafone | - |
R3‑080406 | MBMS Considerations for HSPA Evolution | Vodafone | proposal 1) as agreed requirement into TR |
R3‑080407 | MBSFN DOB | IPWireless, Nextwave Wireless | - |
R3‑080408 | LS on TAU in Connected Mode (C1-080392-LS-out Source: CT1, To: TSG SA WG2, Cc: TSG RAN WG2,TSG RAN WG3) | CT1 | reply to S2-075870=R3-080030 |
R3‑080409 | Reply LS on Area and Access Restrictions (C1-080394 Source: CT1, To: TSG RAN WG3, Cc: TSG RAN WG2,TSG SA WG2) | CT1 | reply to R3-072395 |
R3‑080410 | Retransmission of UL and DL NAS messages during inter-eNB handovers (C1-080399 LS on retrans and dup detection Source: CT1, To: TSG RAN WG2,TSG RAN WG3, Cc: ) | CT1 | reply to R2-075457=R3-080016 |
R3‑080411 | Response LS on inter-MME load balancing, Attach/TAU/Service Request procedures and corresponding RRC/S1 connection establishment procedures (C1-080572-LSout Source: CT1, To: TSG SA WG2, Cc: TSG RAN WG2 RAN3) | CT1 | reply to S2-080991=R3-080044 |
R3‑080412 | LS on outstanding NAS messages (C1-080574-LS-out Source: CT1, To: TSG SA WG3, Cc: TSG RAN WG2,TSG RAN WG3,TSG SA WG2) | CT1 | reply to S3a071035=R3-080053 |
R3‑080413 | UE History Information | Vodafone | - |
R3‑080414 | Inclusion of EARFCN into Last visited cell information | Vodafone | wait for RAN2 |
R3‑080415 | UL DPDCH Indicator for E-DCH Operation in RL Setup in RNSAP and NBAP | NEC | - |
R3‑080416 | Correction the condition of UL DPDCH Indicator for E-DCH Operation | NEC | - |
R3‑080417 | Correction the condition of UL DPDCH Indicator for E-DCH Operation | NEC | - |
R3‑080418 | Correction the condition of UL DPDCH Indicator for E-DCH Operation | NEC | - |
R3‑080419 | Correction the condition of UL DPDCH Indicator for E-DCH Operation | NEC | - |
R3‑080420 | Inter-RAT/Frequency Automatic Neighbor Relation Measurements | Ericsson | 36.300 |
R3‑080421 | The value range of MME UE S1AP ID | Ericsson | - |
R3‑080422 | Introduction of TNL association | Ericsson | - |
R3‑080423 | Correction of ASN.1 inconsistencies | Ericsson | agreed for big CR |
R3‑080424 | 3G home NodeB architecture | Ericsson | - |
R3‑080425 | Reply LS on Earthquake and Tsunami Warning System (G2-080112 Source: TSG GERAN WG2, To: TSG SA WG2,TSG SA WG1,TSG GERAN,TSG GERAN WG1, Cc: TSG RAN WG2,TSG RAN WG3,CT1,TSG SA WG3) | TSG GERAN WG2 | - |
R3‑080426 | Handover Cancellation procedure for S1 and X2 handover | NTT DoCoMo, Inc. | - |
R3‑080427 | Location Reporting procedure on S1 | NTT DoCoMo, Inc. | - |
R3‑080428 | Revised draft report of RAN3#58, Jeju Island, Korea | MCC | - |
R3‑080429 | LS on GAN Iu mode | RAN3 | - |
R3‑080430 | Workplan and Working Procedures v0.29.0 (Rel-7) | MCC | - |
R3‑080431 | Proposed Text for E-MBMS architecture in 36.401 | ZTE | agreed for big CR |
R3‑080432 | Description of Mobility Management in 36.401 | NEC | agreed for big CR |
R3‑080433 | Definition of logical synchronisation port for phase- and time-synchronisation | Ericsson | agreed for big CR |
R3‑080434 | LS on Changes to the format of TMGI | RAN3 | - |
R3‑080435 | Introduction of new Configuration Rule for Extended RNC ID Scheme | Nokia Siemens Networks, Nokia | 25.999 |
R3‑080436 | Correction on MAC-d PDU Size for E-DCH | Nokia Siemens Networks, Nokia | - |
R3‑080437 | Correction on MAC-d PDU Size for E-DCH | Nokia Siemens Networks, Nokia | - |
R3‑080438 | Correction on Abnormal Condition for identical cell on HSDPA/E-DCH Serving Cell | Nokia Siemens Networks, Nokia | - |
R3‑080439 | Correction on Abnormal Condition for identical cell on HSDPA/E-DCH Serving Cell | Nokia Siemens Networks, Nokia | - |
R3‑080440 | Addition of IE "Continuous Packet Connectivity HS-SCCH less Deactive Indicator" | Huawei | - |
R3‑080441 | Addition of IE "Continuous Packet Connectivity HS-SCCH less Deactive Indicator" | Huawei | - |
R3‑080442 | Introduction of an additional UE Category for 1.28Mcps TDD E-DCH | CATT, TD-TECH, ZTE | - |
R3‑080443 | Introduction of an additional UE Category for 1.28Mcps TDD E-DCH | CATT, TD-TECH, ZTE | - |
R3‑080444 | Supporting multi-frequency operation on MBMS for 1.28Mcps TDD | CMCC, RITT, CATT,TD Tech, ZTE, Spreadtrum Communic | - |
R3‑080445 | Introduction of multi-frequency operation for HSUPA for 1.28Mcps TDD | CMCC, RITT, CATT,TD Tech, ZTE, Spreadtrum Communic | - |
R3‑080446 | EUL power control gap for 1.28Mcps TDD | TD Tech Ltd. | no agreement in RAN1 |
R3‑080447 | EUL power control gap for 1.28Mcps TDD | TD Tech Ltd. | no agreement in RAN1 |
R3‑080448 | LS on CSG related mobility (stage2 text) (R2-075478 Source: TSG RAN WG2, To: TSG SA WG1,TSG RAN WG4,TSG GERAN, Cc: TSG RAN WG3,TSG SA WG2,CT1,TSG SA WG3) | TSG RAN WG2 | - |
R3‑080449 | Reply LS on Signalling of additional spectrum emission requirements | RAN3 | - |
R3‑080450 | Security information transfer in Handover procedure | Huawei | - |
R3‑080451 | Reply LS on mechanism to support reordering in target eNB (C4-080422 Source: CT4, To: TSG SA WG2,TSG RAN WG3, Cc: ) | CT4 | - |
R3‑080452 | [DRAFT] LS on RAN3 requirements for GTPv2 (C4-080449_LS_RAN3_GTP Source: TSG CT WG4, To: TSG RAN WG3, Cc: TSG SA WG2) | TSG CT WG4 | - |
R3‑080453 | Introduction of automatic neighbour relation function | Ericsson | attach to LS |
R3‑080454 | Inter-RAT/Frequency Automatic Neighbor Relation Measurements | Ericsson | 36.300 |
R3‑080455 | LS Automatic Neighbour Relation Function | Ericsson | - |
R3‑080456 | Mobility Robustness Optimization Use Case | Huawei | - |
R3‑080457 | LS on Measurements for self optimisation of cell selection/reselection parameters | NEC | - |
R3‑080458 | Mobility Load Balancing Optimization Use Case | Huawei,Telecom Italia | - |
R3‑080459 | Coverage and Capacity Optimization Use Case Description | Huawei, Alcatel-Lucent | - |
R3‑080460 | Energy savings and Interference reduction SON Use case | Alcatel-Lucent | - |
R3‑080461 | DRAFT LS on RAN performance monitoring | NTT DoCoMo | - |
R3‑080462 | LS on security aspects for Home eNB | Orange | - |
R3‑080463 | Inclusion of Cell Id into common measurement report | Vodafone, Nokia Siemens Networks, Nokia, T-Mobile | - |
R3‑080464 | S1 Connection for home eNodeB | Huawei, Samsung | agreed for TR R3.020 |
R3‑080465 | Impact on S1AP from HeNB GW concept | Nokia Siemens Networks, Mitsubishi Electric | - |
R3‑080466 | Draft Reply LS on RAN3 requirements for GTPv2 | Fujitsu | postponed to next meeting |
R3‑080467 | Reply LS on Earthquake and Tsunami Warning System | NTT DoCoMo | - |
R3‑080468 | LS on the necessity of Location Reporting procedure in S1 | NTT DoCoMo | - |
R3‑080469 | Data link layer proposal | Alcatel-Lucent | - |
R3‑080470 | Data link layer proposal | Alcatel-Lucent | - |
R3‑080471 | Inter-RAT/Frequency Automatic Neighbor Relation Measurements | Ericsson | 36.300, wait for LS reply |
R3‑080472 | LS Automatic Neighbour Relation Function | RAN3 | - |
R3‑080473 | LTE Stage 2 handling end marker packets | Fujitsu | 36.300 |
R3‑080474 | RAN3 corrections to 36.300 | Ericsson | - |
R3‑080475 | Finalisation of X2 Release Resource behaviour | Ericsson | agreed for 36.300 |
R3‑080476 | TR on self Configuring and Self Optimizing Network Use Cases and Functional description | T-Mobile | - |
R3‑080477 | LS on Self Configuring and Self Optimizing Network Use Cases and Functional description TR | T-Mobile | - |
R3‑080478 | Maintaining Hyper Frame Number at handover | Ericsson | agreed for big CR |
R3‑080479 | FFS removal from 36.423 | Nokia Siemens Networks, Nokia | - |
R3‑080480 | UL PDCP SN handling | Ericsson | agreed for big CR |
R3‑080481 | Selective forwarding for completion of S1 based handover | Alcatel-Lucent | - |
R3‑080482 | DRAFT LS on Applicability of “subscriber type” indication for UTRAN & GERAN | Vodafone | - |
R3‑080483 | Correction of Trace Depth IE | Ericsson | email check until 20 Feb |
R3‑080484 | Correction of Trace Depth IE | Ericsson | email check until 20 Feb |
R3‑080485 | Overspecification of the bearer type | Alcatel-Lucent | agreed for big CR |
R3‑080486 | Report of 3G HNB discussions | Nokia Siemens Networks | - |
R3‑080487 | text proposal to TR 25.820 | Nokia Siemens Networks | - |
R3‑080488 | UE context modification procedure | Nokia Siemens Networks, Nokia, Huawei | agreed for big 36.300 CR |
R3‑080489 | Security key update function on the S1 interface | Nokia Siemens Networks, Nokia | agreed for big CR |
R3‑080490 | Correction on HS-DSCH MAC-d PDU Size Format IE in HS-DSCH Information to Modify | Nokia Siemens Networks, Nokia | - |
R3‑080491 | Correction on HS-DSCH MAC-d PDU Size Format IE in HS-DSCH Information to Modify | Nokia Siemens Networks, Nokia | - |
R3‑080492 | Addition of MME-Initiated S1 UE Context Release to S1AP | Ericsson | agreed for big CR |
R3‑080493 | text proposal to TR 25.820 | TeliaSonera, Kineto, Nokia Siemens Networks, Huawei | - |
R3‑080494 | On Interworking with legacy CN | Nokia Siemens Networks, Nokia | R3.021 |
R3‑080495 | LS on UTRAN enhancements for the support of inter-cell interference cancellation | Qualcomm Europe | - |
R3‑080496 | Current MBMS Service over flat architecture | Nokia Siemens Networks, Nokia | R3.022 |
R3‑080497 | Proposal for MBMS Improvement over flat architecture | Nokia Siemens Networks, Nokia | R3.022, email check until 20 Feb |
R3‑080498 | MBMS over HSPA+ | Huawei | R3.021 |
R3‑080499 | report on CS call establishment enhancement to TSG-RAN | Huawei | to be reported to TSG-RAN |
R3‑080500 | Introduction of DOB for MBSFN operation | Ericsson | - |
R3‑080501 | Introduction of the Improved L2 in the uplink | Nokia Siemens Networks, Nokia | - |
R3‑080502 | Introduction of UMTS 700 MHz (Bands XII XIV) in 25.461 | Alcatel-Lucent | - |
R3‑080503 | Inclusion of Cell Id into common measurement report | Vodafone, Nokia Siemens Networks, Nokia, T-Mobile | - |
R3‑080504 | S1 CDMA2000 Tunneling Procedure | Nokia Siemens Networks, Nokia,ricsson, Alcatel-Lucent, Motorola, Nortel, Verizon | agreed for big CR |
R3‑080505 | stage 2 update for handling of end marker packet in eUTRAN | Fujitsu | 36.300 |
R3‑080506 | Introduction of Improved L2 for Uplink | Ericsson | - |
R3‑080507 | Adding IMSI in Paging | NEC | agreed for big CR |
R3‑080508 | LTE ETWS architecture | Nokia Siemens Network | - |
R3‑080509 | Completion of TX2relocoverall | Alcatel-Lucent, Nortel | agreed for big CR |
R3‑080510 | Adding 'Cause' and Cause Value for X2 Handover Request | Nokia Siemens Networks, Nokia | - |
R3‑080511 | LS on RFL Recovery Information over X2 | Nortel | - |
R3‑080512 | S1 Setup Ids correction | Nortel | - |
R3‑080513 | X2 Setup Ids correction | Nortel | - |
R3‑080514 | Home eNB attachment scenario | Orange | - |
R3‑080515 | LS on LTE-cell- and eNB-identification | Nokia Siemens Networks | - |
R3‑080516 | Area restriction in Shared networks | Ericsson | agreed for big CR |
R3‑080517 | Correction the condition of UL DPDCH Indicator for E-DCH Operation | NEC | - |
R3‑080518 | Correction the condition of UL DPDCH Indicator for E-DCH Operation | NEC | - |
R3‑080519 | Correction the condition of UL DPDCH Indicator for E-DCH Operation | NEC | - |
R3‑080520 | Correction the condition of UL DPDCH Indicator for E-DCH Operation | NEC | - |
R3‑080521 | PHY_ID Automatic Configuration | Nokia Siemens Network | - |
R3‑080522 | Addition of IE "Continuous Packet Connectivity HS-SCCH less Deactive Indicator" | Huawei | email checking until Wednesday20 Feb |
R3‑080523 | Addition of IE "Continuous Packet Connectivity HS-SCCH less Deactive Indicator" | Huawei | email checking until Wednesday20 Feb |
R3‑080524 | TR on self Configuring and Self Optimizing Network Use Cases and Functional description | T-Mobile | - |
R3‑080525 | Mobility Load Balancing Optimization Use Case | Huawei,Telecom Italia | - |
R3‑080526 | Mobility Robustness Optimization Use Case | Huawei | email check |
R3‑080527 | LS on Measurements for self optimisation of cell selection/reselection parameters | NEC | email check until 20th Feb |
R3‑080528 | Energy savings and Interference reduction SON Use case | Alcatel-Lucent | - |
R3‑080529 | PHY_ID Automatic Configuration | Nokia Siemens Network | - |
R3‑080530 | LS on RAN performance monitoring | RAN3 | - |
R3‑080531 | LS on Self Configuring and Self Optimizing Network Use Cases and Solutions | T-Mobile | - |
R3‑080532 | UE capability info provision | Nokia Siemens Networks, Nokia | agreed for big CR |
R3‑080533 | Adding 'Cause' and Cause Value for X2 Handover Request | Nokia Siemens Networks, Nokia | - |
R3‑080534 | FFS removal from 36.423 | Nokia Siemens Networks, Nokia | agreed for big CR |
R3‑080535 | adhcoc session on eUTRAN and EPS ids | Chenghock | - |
R3‑080536 | LS on Self Configuring and Self Optimizing Network Use Cases and Solutions | RAN3 | - |
R3‑080537 | LS on security aspects for Home eNB | Orange | - |
R3‑080538 | LS on security aspects for Home eNB | RAN3 | - |
R3‑080539 | Impact on S1AP from HeNB GW concept | Nokia Siemens Networks, Mitsubishi Electric | email discussion until 20th Feb |
R3‑080540 | Reply LS on Earthquake and Tsunami Warning System | NTT DoCoMo | - |
R3‑080541 | Reply LS on Earthquake and Tsunami Warning System | RAN3 | - |
R3‑080542 | LS on the necessity of Location Reporting procedure in S1 | NTT DoCoMo | - |
R3‑080543 | LS on Applicability of “subscriber type” indication for UTRAN & GERAN | RAN3 | - |
R3‑080544 | S1 Setup Ids correction | Nortel | agreed for big CR |
R3‑080545 | X2 Setup Ids correction | Nortel | agreed for big CR |
R3‑080546 | LS on LTE-cell- and eNB-identification | Nokia Siemens Networks | - |
R3‑080547 | LS on LTE-cell- and eNB-identification | RAN3 | - |
R3‑080548 | LS on UTRAN enhancements for the support of inter-cell interference cancellation | RAN3 | - |
R3‑080549 | Introduction of Improved L2 for Uplink | Ericsson | - |
R3‑080550 | Introduction of Improved L2 for Uplink | Ericsson | - |
R3‑080551 | Selective forwarding for completion of S1 based handover | Alcatel-Lucent | email check until 20 Feb |
R3‑080552 | Adding 'Cause' and Cause Value for X2 Handover Request | Nokia Siemens Networks, Nokia | agreed for big CR |
R3‑080553 | LS on RLF Recovery Information over X2 | RAN3 | - |
R3‑080554 | LS on RLF Recovery Information over X2 | RAN3 | not needed |
R3‑080555 | text proposal to TR 25.820 | TeliaSonera, Kineto, Nokia Siemens Networks, Huawei | - |
R3‑080556 | LS on test proposal to TR 25.820 | RAN3 | - |
R3‑080557 | Cell’s Physical ID Automated Configuration | Nokia Siemens Network | - |
R3‑080558 | RAN3 agreed changes for TS 36.401 | NEC | - |
R3‑080559 | RAN3 agreed changes for TS 36.413 | Nokia Siemens Networks | - |
R3‑080560 | RAN3 agreed changes for TS 36.423 | Ericsson | - |
R3‑080561 | Impacts of RRC GANSS changes | Alcatel-Lucent, Thales | - |
R3‑080562 | Addition of IE "Continuous Packet Connectivity HS-SCCH less Deactive Indicator" | Huawei | - |
R3‑080563 | Addition of IE "Continuous Packet Connectivity HS-SCCH less Deactive Indicator" | Huawei | - |
R3‑080564 | LS on the necessity of Location Reporting procedure in S1 | RAN3 | - |
R3‑080565 | LS on Measurements for self optimisation of cell selection/reselection parameters | RAN3 | email check until 20th Feb |
R3‑080566 | Energy savings and Interference reduction SON Use case | Alcatel-Lucen | - |
page generated from database: 2024-07-20 12:15:34