3GPP TDocs (written contributions) at meeting
Meeting: R3-60 - 2008-05-05 to 2008-05-09, Kansas City
meeting id: R3-60 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
R3‑081015 | Agenda RAN3#60, Kansas City, USA, 05 -09 May 2008 | Chairman | - |
R3‑081016 | Revised report of RAN3#59bis, Shenzhen, China | MCC | - |
R3‑081017 | Report of the 3GPP TSG RAN IMT Advanced Workshop and summary of LTE advanced requirements | MCC | - |
R3‑081018 | RAN3 agreed changes to TS 36.300 | Ericsson | was R3-081008 in Shenzen |
R3‑081019 | Frequency synchronization requirements in case of Synchronous Ethernet synchronization method | Orange | agreed for 36.401 |
R3‑081020 | RAN3 agreed changes for TS 36.401 | NEC | was R3-081002 in Shenzhen |
R3‑081021 | SCTP flow control and overload protection | Ericsson | was R3-080991 in Shenzhen |
R3‑081022 | SCTP flow control and overload protection | Ericsson | was R3-080974 in Shenzhen |
R3‑081023 | Redundancy of the SCTP endpoint | Alcatel-Lucent | was R3-081005 in Shenzhen |
R3‑081024 | RAN3 agreed changes for TS 36.413 | Nokia Siemens Networks | was R3-081003 in Shenzhen |
R3‑081025 | RAN3 agreed changes for TS 36.423 | Ericsson | was R3-081004 in Shenzhen |
R3‑081026 | Introduction of LCR TDD 64QAM in RNSAP | ZTE, RITT, CATT, TD-TECH, Spreadtrum Communication | was R3-080957 in Shenzhen |
R3‑081027 | Introduction of LCR TDD 64QAM in NBAP | ZTE, RITT, CATT, TD-TECH, Spreadtrum Communication | was R3-080956 in Shenzhen |
R3‑081028 | Status Report: Enhancements for SRNS Relocation Procedure | Nokia Siemens Networks | - |
R3‑081029 | Status Report: Enhancements for FDD HSPA Evolution | Nokia Siemens Networks | - |
R3‑081030 | LS on LTE-cell- and eNB-identification (C1-081422-LS-out Source: CT1, To: TSG RAN WG3, Cc: TSG RAN WG2,TSG SA WG2) | CT1 | reply to R3-080547 |
R3‑081031 | Reply LS on frequency restrictions (C1-081427_LS OUT on Frequency restrictions Source: CT1, To: TSG RAN WG3, Cc: TSG SA WG2,TSG RAN WG2) | CT1 | reply to R3-080979 |
R3‑081032 | Reply LS on NAS–AS interaction for dependent procedures (C1-081433 Source: CT1, To: TSG RAN WG2, Cc: TSG RAN WG3,TSG SA WG2) | CT1 | reply to R2-082047 |
R3‑081033 | LS on Messaging Support for Network Based Location Technologies on User Plane (C4-081019 Source: TSG CT WG4, To: TSG SA WG2,OMA LOC, Cc: TSG RAN WG2,TSG RAN WG3) | TSG CT WG4 | - |
R3‑081034 | Reply to LS on applicability of “subscriber type” indication for UTRAN & GERAN (G2-080228 Source: TSG GERAN WG2, To: TSG SA WG2,TSG RAN WG3,TSG RAN WG2, Cc: TSG GERAN,CT1) | TSG GERAN WG2 | reply to R3-080543 |
R3‑081035 | LS on MAC-d flow definition for MAC-ehs. (R2-081934 Source: TSG RAN WG2, To: TSG RAN WG3, Cc: ) | TSG RAN WG2 | - |
R3‑081036 | Reply LS on “Changes to the format of TMGI” (R2-081971 Source: TSG RAN WG2, To: TSG RAN WG3, Cc: CT4) | TSG RAN WG2 | reply to R3-080434 |
R3‑081037 | LS on EPS Session management procedure optimizations (R2-082032 Source: TSG RAN WG2, To: CT WG1, Cc: TSG RAN WG3,CT WG4) | TSG RAN WG2 | reply to C1-080780=R3-080597 (leftover from RAN#59bis) |
R3‑081038 | Response LS to LS on RLF Recovery Information over x2 (R2-082033 Source: TSG RAN WG2, To: TSG RAN WG3, Cc: ) | TSG RAN WG2 | reply to R3-080553 |
R3‑081039 | Reply LS on Location Reporting procedure (R2-082034 Source: TSG RAN WG2, To: TSG RAN WG3,TSG SA WG2, Cc: ) | TSG RAN WG2 | reply to R3-080564 |
R3‑081040 | Reply LS on LTE-cell- and eNB-identification (R2-082041 Source: TSG RAN WG2, To: TSG RAN WG3,CT1, Cc: TSG SA WG2,CT4) | TSG RAN WG2 | reply to R3-080547 |
R3‑081041 | LS on Half-Duplex FDD (R4-080805 Source: TSG RAN WG4, To: TSG RAN WG2, Cc: TSG RAN WG1,TSG RAN WG3) | TSG RAN WG4 | - |
R3‑081042 | LS reply on “subscriber type” indication via S1 (S2-083105_RFSP-LS-to-RAN2.pa3 Source: TSG SA WG2, To: TSG RAN WG2, Cc: TSG RAN WG3) | TSG SA WG2 | reply to R2-081355=R3-080583 |
R3‑081043 | Reply LS on ”Principles on Idle Mode Signalling Reduction” (S2-083116 Source: TSG SA WG2, To: TSG RAN WG2, Cc: CT1,CT4,TSG RAN WG3) | TSG SA WG2 | reply to R2-075462=R3-080006 |
R3‑081044 | LS on Earthquake and Tsunami Warning System (S2-083168 Source: TSG SA WG2, To: TSG RAN WG3,TSG RAN WG2,TSG RAN WG1,CT1,TSG SA WG1,TSG SA WG3,TSG GERAN,TSG GERAN WG2, Cc: ) | TSG SA WG2 | - |
R3‑081045 | Reply LS on inter-MME load balancing, Attach/TAU/Service Request procedures and corresponding RRC/S1 connection establishment procedures (S2-083171 Source: TSG SA WG2, To: TSG RAN WG2, Cc: TSG RAN WG3,CT1,TSG SA WG3) | TSG SA WG2 | reply to R2-081380=R3-080586 |
R3‑081046 | Reply LS on the necessity of Location Reporting procedure in S1 (S2-083174_e-mail-appd-S2-083162 Source: TSG SA WG2, To: TSG RAN WG2,TSG RAN WG3, Cc: ) | TSG SA WG2 | replt to R3-080564 |
R3‑081047 | Follow up LS on Earthquake and Tsunami Warning System (S3-080522 Source: TSG SA WG3, To: TSG RAN WG3,TSG RAN WG2, Cc: TSG SA WG2) | TSG SA WG3 | - |
R3‑081048 | RACH Optimisation use case description | 'NTT DoCoMo, T-Mobile, Orange, Vodafone, Telecom Italia' | 36.300 |
R3‑081049 | Way Forward on NW Interface for ETWS support | 'NTT DoCoMo, Panasonic, Nokia Siemens Networks | - |
R3‑081050 | Impact of inter eNB Handover on Location Reporting procedure | NTT DoCoMo | - |
R3‑081051 | Handover Cancellation timing | 'NTT DoCoMo, NEC, Alcatel-Lucent | - |
R3‑081052 | Handover Cancellation timing | 'NTT DoCoMo, NEC, Alcatel-Lucent' | - |
R3‑081053 | Handover Cancellation timing | 'NTT DoCoMo, NEC | - |
R3‑081054 | A way forward for PPAC | NTT DoCoMo | - |
R3‑081055 | LS on E-AICH Power Offset and Error Targets for AICH/E-AICH (R1-081702 Source: TSG RAN WG1, To: TSG RAN WG2,TSG RAN WG3,TSG RAN WG4, Cc: ) | TSG RAN WG1 | - |
R3‑081056 | LS on additional RSRP trigger for ICIC (R1-081704 Source: TSG RAN WG1, To: TSG RAN WG2, Cc: TSG RAN WG3) | TSG RAN WG1 | - |
R3‑081057 | LS on Subscriber and Equipment Trace for EPC and E-UTRAN (S5-080878 Source: TSG SA WG5, To: CT1,CT4,TSG RAN WG3, Cc: ) | TSG SA WG5 | - |
R3‑081058 | Bandwidth requirements under 3G HNB architectures | ip.access Ltd | - |
R3‑081059 | Architectural impacts of market requirements for bandwidth optimisation | ip.access Ltd | 25.820 |
R3‑081060 | Support of Hand-In for Home Node B | Ip.access Ltd | 25.820 |
R3‑081061 | Notes on Home node B architecture | Ip.access Ltd | 25.820 |
R3‑081062 | Messaging Support for Network Based Location Technologies on User-Plane | Polaris WirelessPolaris Wireless, TruePosition, AT&T | - |
R3‑081063 | Addition of "Network Location Information" indicator in the Location Related Data Request Type IE | Polaris Wireless, TruePosition, AT&T | - |
R3‑081064 | Adding the S-TMSI into the INITIAL UE MESSAGE | CATT | - |
R3‑081065 | FFS removal on paging repetition | CATT | agreed for 36.413 |
R3‑081066 | Introduction of trace activation during S1 handover | CATT | agreed for 36.300 |
R3‑081067 | Introduction of trace activation during S1 handover | CATT | - |
R3‑081068 | New attribute for Neighbor Relation Table | CATT, CMCC | 36.300 |
R3‑081069 | Mechanism for Scheduling Information transmission on MAC-e PDU alone for 1.28 Mcps TDD in EUL | CATT | - |
R3‑081070 | Mechanism for Scheduling Information transmission on MAC-e PDU alone for 1.28 Mcps TDD in EUL | CATT | - |
R3‑081071 | Mechanism for Scheduling Information transmission on MAC-e PDU alone for 1.28 Mcps TDD in EUL | CATT | - |
R3‑081072 | Mechanism for Scheduling Information transmission on MAC-e PDU alone for 1.28 Mcps TDD in EUL | CATT | - |
R3‑081073 | Increase of the precision of the Reference Beta for 1.28 Mcps TDD EUL | CATT | - |
R3‑081074 | Increase of the precision of the Reference Beta for 1.28 Mcps TDD EUL | CATT | - |
R3‑081075 | Increase of the precision of the Reference Beta for 1.28 Mcps TDD EUL | CATT | - |
R3‑081076 | Increase of the precision of the Reference Beta for 1.28 Mcps TDD EUL | CATT | - |
R3‑081077 | Modification of E-HICH Time Offset configuration for LCR TDD | ZTE,CATT,TD TECH | - |
R3‑081078 | Modification of E-HICH Time Offset configuration for LCR TDD | ZTE,CATT,TD TECH | - |
R3‑081079 | HNB Abbreviations alignment adjustment | ZTE | - |
R3‑081080 | Access Control in 3G HNB Network | ZTE | - |
R3‑081081 | Introduction of cause values for X2 handover | ZTE, CMCC | - |
R3‑081082 | Introduction of cause values for X2 handover | ZTE, CMCC | - |
R3‑081083 | Add AMBR in HANDOVER REQUEST message | ZTE | agreed for 36.413 |
R3‑081084 | Modify the presence of UE Identity Index value in Paging message | ZTE | - |
R3‑081085 | Correction the description for eNB UE S1AP ID | ZTE | agreed for 36.401 |
R3‑081086 | Correction on X2 Reset message | ZTE | - |
R3‑081087 | Further consideration on architecture for MBMS over HSPA+ | ZTE | - |
R3‑081088 | Two basic SON functionalities for 3G HNBs | Qualcomm Europe, T-Mobile | - |
R3‑081089 | Requirements on Gateway Functionalities for HeNB Support | Qualcomm Europe | - |
R3‑081090 | Automatic Physical Cell Identity Selection in LTE: Requirements and Solutions | Qualcomm Europe, T-Mobile | - |
R3‑081091 | E-DCH Resource Release in CELL_FACH | Qualcomm Europe | - |
R3‑081092 | Common E-DCH resource usage report | Qualcomm Europe | - |
R3‑081093 | Handling of partial failures during EPS bearer set up | Qualcomm Europe | - |
R3‑081094 | Skeleton of TR36.913 "Requirements for LTE-Advanced" | LTE-Advanced rapporteur (NTT DoCoMo) | - |
R3‑081095 | improvement on PRB-based load balancing | China Mobile, Huawei, KPN | - |
R3‑081096 | TRSON: reference to the stage 2 for the ANRF | Alcatel-Lucent | 36.902 |
R3‑081097 | Specification of Handover causes in LTE | Alcatel-Lucent | - |
R3‑081098 | Correction of Handover cause values over X2 | Alcatel-Lucent | - |
R3‑081099 | Specification of new handover causes in LTE | Alcatel-Lucent | - |
R3‑081100 | Introduction of new handover cause values over X2 | Alcatel-Lucent | - |
R3‑081101 | Introduction of new handover cause values over S1 | Alcatel-Lucent | - |
R3‑081102 | S1 Specification Principles to succeed the IOT | Alcatel-Lucent, NEC, NSN, Nortel, Nokia, Motorota,Orange | - |
R3‑081103 | Specification Principles for S1AP | Alcatel-Lucent, NEC, NSN, Nortel, Nokia, Motorota,,Orange | - |
R3‑081104 | X2 Specification Principles to succeed the IOT | Alcatel-Lucent, NEC, Nokia Siemens Network, Nortel, Nokia, Motorola, Samsung, Vodafone, Orange | - |
R3‑081105 | Specification Principles for X2AP | Alcatel-Lucent, NEC, NSN, Nortel, Nokia, Motorota,,Orange | - |
R3‑081106 | Cell identifiers over S1 and X2 in LTE | Alcatel-Lucent | - |
R3‑081107 | Cell identification over X2 | Alcatel-Lucent | - |
R3‑081108 | Cell identification over S1 | Alcatel-Lucent | - |
R3‑081109 | Interaction of Bearer Release and Handover procedures | Alcatel-Lucent | - |
R3‑081110 | Management of the S-TMSI | Alcatel-Lucent | - |
R3‑081111 | Management of the S-TMSI | Alcatel-Lucent | - |
R3‑081112 | Relation between S1 Setup and Reset procedures | Alcatel-Lucent, NEC | - |
R3‑081113 | Relation between S1 Setup and Reset procedures | Alcatel-Lucent, NEC | - |
R3‑081114 | Misalignment of cause "unspecified" | Alcatel-Lucent | - |
R3‑081115 | Correction of tunnel endpoints | Alcatel-Lucent | - |
R3‑081116 | Fresh forwarding indication over X2 | Alcatel-Lucent | - |
R3‑081117 | Correction of the QoS | Alcatel-Lucent | - |
R3‑081118 | Rejection causes over X2 | Alcatel-Lucent | - |
R3‑081119 | Rejection causes over X2 | Alcatel-Lucent | - |
R3‑081120 | Self-configuration of the type of handover | Alcatel-Lucent | agreed for 36.423 |
R3‑081121 | HNBs Location Certification | Mitsubishi Electric | - |
R3‑081122 | HeNBs and X2 interface | Mitsubishi Electric | - |
R3‑081123 | Dynamic Setup of HNBs for Energy Savings and Interference Reduction | Mitsubishi Electric | - |
R3‑081124 | Support of emergency calls | Vodafone | - |
R3‑081125 | Correction on "Enhancements to Macro Diversity & Cell Interference Control" | Huawei, Nokia, Nokia Siemens Network | - |
R3‑081126 | Correction on "Enhancements to Macro Diversity & Cell Interference Control" | Huawei, Nokia, Nokia Siemens Network | - |
R3‑081127 | Correction on "Enhancements to Macro Diversity & Cell Interference Control" | Huawei, Nokia, Nokia Siemens Network | - |
R3‑081128 | Correction on "Enhancements to Macro Diversity & Cell Interference Control" | Huawei, Nokia, Nokia Siemens Network | - |
R3‑081129 | Correction on "Enhancements to Macro Diversity & Cell Interference Control" | Huawei, Nokia, Nokia Siemens Network | - |
R3‑081130 | E-FACH Measurement Report | Huawei | - |
R3‑081131 | E-FACH Measurement Report | Huawei | - |
R3‑081132 | E-FACH Measurement Report | Huawei | - |
R3‑081133 | UE Capability | Huawei, Ericsson | - |
R3‑081134 | Handover Trigger message for Load Re-balancing | Huawei, Ericsson | - |
R3‑081135 | Intra-Cell Handover Trigger procedure for the S1 interface | Huawei, Ericsson | - |
R3‑081136 | Intra-Cell Handover Trigger procedure for the S1 interface | Huawei, Ericsson | - |
R3‑081137 | Relation between Load Balancing and Load Re-balancing | Huawei, Ericsson, China Mobile | - |
R3‑081138 | MME re-allocation function | Huawei, Ericsson | - |
R3‑081139 | Addition of Location reporting procedure | Huawei, NTT DoCoMo | - |
R3‑081140 | Addition of Location Reporting Procedure (CR 36.413) | Huawei, NTT DoCoMo | - |
R3‑081141 | Addition of Location reporting procedure (36.300) | Huawei, NTT DoCoMo | - |
R3‑081142 | Subscriber type Transfer over S1 and X2 | Huawei | - |
R3‑081143 | Subscriber Type Transfer over S1 | Huawei | - |
R3‑081144 | Subscriber Type Transfer over X2 | Huawei | - |
R3‑081145 | Discussion on the AP ID Uniqueness | Huawei | - |
R3‑081146 | Downlink Detection Functionality for HNB | Huawei | - |
R3‑081147 | Discussion on E-RNTI allocation for enhanced Cell_FACH | Huawei | - |
R3‑081148 | Consideration on UTRA HNB active mode mobility | Huawei | - |
R3‑081149 | Correction of the description for NNSF and paging area | Huawei | tbc |
R3‑081150 | Home eNB Registration | Huawei | - |
R3‑081151 | Discussion on U-Plane handling for home eNB | Huawei, Ericsson | - |
R3‑081152 | Discussion on C-Plane handling for home eNB | Huawei | - |
R3‑081153 | NAS PDU of SAE BEARER RELEASE COMMAND | Huawei | wait for RAN2 |
R3‑081154 | MME UE S1AP ID should be optional in UE CONTEXT RELEASE COMPLETE | Huawei | - |
R3‑081155 | Adding IEs in the INITIAL UE MESSAGE message | Huawei | - |
R3‑081156 | CGI transmission in PATH SWITCH REQUEST message | Huawei | - |
R3‑081157 | Exchange of S1 Interface Information between eNBs on X2 | Huawei | - |
R3‑081158 | Specific cause value for X2 handover preparation failure | Huawei | - |
R3‑081159 | Specific cause value for X2 handover preparation failure | Huawei | - |
R3‑081160 | CS capability of network for CS fallback | Huawei | - |
R3‑081161 | User type indication for Inter-RAT HO | Huawei | - |
R3‑081162 | How to modify the eNB ID | Huawei | - |
R3‑081163 | Principles for intra frequency load balancing | Huawei | - |
R3‑081164 | Solutions for the Coverage and Capacity Optimisation use case | Huawei | - |
R3‑081165 | Solutions for the Mobility Robustness use case | Huawei | - |
R3‑081166 | Iu-based 3G HNB Architecture | Huawei | - |
R3‑081167 | Some Identifiers Consideration for 3G HNB | Huawei | - |
R3‑081168 | Consideration on 3G HNB active mode mobility | Huawei | - |
R3‑081169 | Requirement Clarification and Way Forward for HNB Differentiated Charging Function | Huawei | - |
R3‑081170 | Example Signalling Procedure for Centric MBMS Architecture | Huawei | R3-081170 ver3.zip is agreed |
R3‑081171 | Consideration on User Plane Functionality | Huawei | - |
R3‑081172 | Transport efficency improvement for MBMS service by ROHC | Huawei | - |
R3‑081173 | Consideration on Proposal of GGSN Improvement for MBMS over Node B+ | Huawei | - |
R3‑081174 | Solution for interference reduction SON use case | Orange, Alcatel-Lucent | 36.300 |
R3‑081175 | Reference Architecture for 3G HNB Deployments | Kineto Wireless Inc, Motorola, NEC | - |
R3‑081176 | Access Control for 3G HNB Deployments | Alcatel-Lucent, Kineto Wireless, NEC, Motorola | 25.820, R3.020 |
R3‑081177 | Paging Related Issues and Solutions for 3G HNB Deployments | Alcatel-Lucent, Kineto Wireless, NEC, Motorola | 25.820, R3.020 |
R3‑081178 | Discovery and Registration at 3G HNB-GW | Alcatel-Lucent, Kineto Wireless, NEC, Motorola | 25.820, R3.020 |
R3‑081179 | Support for Legacy UTRAN Functions | Kineto Wireless Inc, Motorola, NEC | - |
R3‑081180 | Qos enhancements for 3G HNB Deployments | Kineto Wireless Inc, Motorola, NEC | - |
R3‑081181 | Protocol Stacks for 3G HNB Deployments | Kineto Wireless Inc, Motorola, NEC | - |
R3‑081182 | S1 connectivity for HeNB | Panasonic | - |
R3‑081183 | HeNB functionality for S1-flex | Panasonic | - |
R3‑081184 | Extended power control gap for E-PUCH in LCR TDD | TD Tech, CATT, ZTE | - |
R3‑081185 | Extended power control gap for E-PUCH in LCR TDD | TD Tech, CATT, ZTE | - |
R3‑081186 | Extended power control gap for E-PUCH in LCR TDD | TD Tech, CATT, ZTE | - |
R3‑081187 | Extended power control gap for E-PUCH in LCR TDD | TD Tech, CATT, ZTE | - |
R3‑081188 | MAC-ehs in CELL_DCH | Alcatel-Lucent | - |
R3‑081189 | Maximum MAC PDU length with TYPE 2 Frame Protocol | Alcatel-Lucent | - |
R3‑081190 | Correction of Maximum MAC-d/c PDU Length IE definition for frame protocol type 2 | Alcatel-Lucent | - |
R3‑081191 | Correction of Maximum MAC-d PDU Length Type 2 IE definition for frame protocol type 2 | Alcatel-Lucent | - |
R3‑081192 | Support of octet aligned HS-DSCH transport block sizes for non-64QAM | Alcatel-Lucent | - |
R3‑081193 | Support of octet aligned HS-DSCH transport block sizes for non-64QAM | Alcatel-Lucent | - |
R3‑081194 | Support of octet aligned HS-DSCH transport block sizes for non-64QAM | Alcatel-Lucent | - |
R3‑081195 | Support of octet aligned HS-DSCH transport block sizes for non-64QAM | Alcatel-Lucent | - |
R3‑081196 | Power Control Gap IE handling | Alcatel-Lucent | - |
R3‑081197 | Power Control Gap IE handling | Alcatel-Lucent | - |
R3‑081198 | Power Control Gap IE handling | Alcatel-Lucent | - |
R3‑081199 | Power Control Gap IE handling | Alcatel-Lucent | replaced by CR in R3-0801420 |
R3‑081200 | Use of UL DPDCH Indicator For E-DCH Operation IE for unsynchronised RL reconfiguration | Alcatel-Lucent | - |
R3‑081201 | UTRAN architecture for the Home Node B | Alcatel-Lucent, Kineto Wireless, NEC, Motorola | 25.820, R3.020 |
R3‑081202 | HNB - Mobility in connected mode | Alcatel-Lucent | 25.820 |
R3‑081203 | Transfer of RANAP messages between 3G HNB and Core Network | Alcatel-Lucent,Kineto Wireless Inc, Motorola, NEC | 25.820 |
R3‑081204 | Latest version of TR 36.902 on "Self-configuring and self-optimizing network use cases and solutions" | T-Mobile | - |
R3‑081205 | S1-U TNL congestion indication | T-Mobile, Orange | - |
R3‑081206 | Trace Support: Support of Configuration and Pulling of Trace Data | T-Mobile, Orange | - |
R3‑081207 | Considerations on automated Phy Cell ID planning | T-Mobile | - |
R3‑081208 | Registration of 3G HNB at the network | Samsung, | - |
R3‑081209 | Mobility Management for 3G HNB | Samsung, | - |
R3‑081210 | UE dedicated and common message analysis | Samsung, | - |
R3‑081211 | Access control | Samsung, | - |
R3‑081212 | Iu-flex supported | Samsung, | - |
R3‑081213 | HeNB Architecture Discussion | Samsung, | - |
R3‑081214 | Registration of HeNB at the network | Samsung | - |
R3‑081215 | S1 Update and Setup | Samsung | - |
R3‑081216 | CR for S1 Update and Setup | Samsung | - |
R3‑081217 | NAS Non Delivery Indication trigger update | Samsung | - |
R3‑081218 | CR for NAS Non Delivery Indication trigger update | Samsung | - |
R3‑081219 | CR Interaction of SAE Bearer release procedure and handover | Samsung | - |
R3‑081220 | CR Introducing S-TMSI to Initial UE Message | Samsung | - |
R3‑081221 | EPS identities | Samsung | - |
R3‑081222 | CR for 36401 on cell identities | Samsung | - |
R3‑081223 | CR for 36423 on cell identities | Samsung | - |
R3‑081224 | CR for 36413 on identities | Samsung | - |
R3‑081225 | Inter-Cell Interference Co-ordination SON Use Case | Alcatel-Lucent, Telecom Italia, CMCC, Orange, Telefonica, T-Mobile, Samsung, Huawei | 36.902 |
R3‑081226 | ANR Neighbors IP address lookup and establishment | Nortel | - |
R3‑081227 | Rapporteur Update for 36.414 and 36.424 | Nortel | - |
R3‑081228 | GTP-U reference for Data Transport | Nortel | - |
R3‑081229 | eGTP draft reference for S1 Data Transport | Nortel | - |
R3‑081230 | eGTP draft reference for X2 Data Transport | Nortel | - |
R3‑081231 | No Removal of the Message Structure IE | Nortel | - |
R3‑081232 | The Message Structure IE | Nortel | - |
R3‑081233 | Return of the Message Structure IE | Nortel | - |
R3‑081234 | Addition of new causes for consistency | Nortel, Alcatel-Lucent | - |
R3‑081235 | MME configuration at S1 Setup | Nortel | - |
R3‑081236 | Abnormal Condition for S1 Setup | Nortel | - |
R3‑081237 | Hardware Load definition | Nortel, Orange | - |
R3‑081238 | Hardware Load introduction | Nortel, Orange | - |
R3‑081239 | TNL Load definition | Nortel, Orange | - |
R3‑081240 | TNL Load introduction | Nortel, Orange | - |
R3‑081241 | None explicit load management with ECN | Nortel | - |
R3‑081242 | Text proposal for ECN introduction on S1 | Nortel | - |
R3‑081243 | Text proposal for ECN introduction on X2 | Nortel | - |
R3‑081244 | IP ECN Congestion Indication for Data Transport | Nortel | - |
R3‑081245 | Text proposal for ECN introduction on S1 Data transport | Nortel | - |
R3‑081246 | Text proposal for ECN introduction on X2 Data transport | Nortel | - |
R3‑081247 | LTE Local Breakout for Home eNB | Nortel | - |
R3‑081248 | Additional tunneled attributes to support LTE to CDMA 1xRTT inter-working | Nortel, Nokia Siemens Networks, Verizon, Alcaterel-Lucent, Ericsson | - |
R3‑081249 | Consideration on MBMS U-plane handling over NodeB+ | CATT | - |
R3‑081250 | Improvement in Master NodeB+/Legacy RNC Solution | CATT | - |
R3‑081251 | RL Parameter Update for E-DCH FDD DL Control Channel Information | Nokia Siemens Networks, Nokia | - |
R3‑081252 | RL Parameter Update for E-DCH FDD DL Control Channel Information | Nokia Siemens Networks, Nokia | - |
R3‑081253 | RL Parameter Update for E-DCH FDD DL Control Channel Information | Nokia Siemens Networks, Nokia | - |
R3‑081254 | RL Parameter Update for E-DCH FDD DL Control Channel Information | Nokia Siemens Networks, Nokia | - |
R3‑081255 | RL Parameter Update for E-DCH FDD DL Control Channel Information | Nokia Siemens Networks, Nokia | - |
R3‑081256 | Clarification on Transport Bearer Not Requested Indicator | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑081257 | Clarification on Transport Bearer Not Requested Indicator | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑081258 | Clarification on Transport Bearer Not Requested Indicator | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑081259 | Clarification on Transport Bearer Not Requested Indicator | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑081260 | Clarification on Transport Bearer Not Requested Indicator | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑081261 | Update of Protocol Model for Enhanced L2 DL Improvement | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑081262 | Stage-3 Proposal for Enhanced Relocation | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑081263 | Introduction of Enhanced Relocation | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑081264 | Introduction of Enhanced Relocation | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑081265 | R3.022 v0.2.0 | Nokia Siemens Networks, Nokia | R3.022 |
R3‑081266 | Synchronisation scheme for Improved GGSN | Nokia Siemens Networks, Nokia | R3-081266_rev1.zip is agreed |
R3‑081267 | GTP-PDU Impact for Improved GGSN | Nokia Siemens Networks, Nokia | R3.022 |
R3‑081268 | Location of PDCP for Improved GGSN | Nokia Siemens Networks, Nokia | R3.022 |
R3‑081269 | O&M Solution for Improved GGSN | Nokia Siemens Networks, Nokia | R3.022 |
R3‑081270 | Solution for PTM<-> PTP switching for Improved GGSN | Nokia Siemens Networks, Nokia, | R3.022, remove scenario 4 |
R3‑081271 | Session Start Handling for Improved GGSN | Nokia Siemens Networks, Nokia | R3.022 |
R3‑081272 | Introduction of Improved L2 for Uplink | Nokia Siemens Networks, Nokia | - |
R3‑081273 | Analysis on NBAP/RNSAP Impact for Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑081274 | Draft CR on TS25.401 for Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑081275 | Draft CR on TS25.425 for Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia, | - |
R3‑081276 | Draft CR on TS25.435 for Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑081277 | Consideration on Iur backward incompatibility problem for Enhanced Uplink in Cell_FACH | Nokia Siemens Networks, Nokia, | - |
R3‑081278 | Impact on FP spec for Enhanced DRX in Cell_FACH | Nokia Siemens Networks, Nokia | - |
R3‑081279 | Impact on NBAP/RNSAP for Enhanced DRX in Cell_FACH | Nokia Siemens Networks, Nokia, | - |
R3‑081280 | Automated Configuration of Physical Cell Identity | Nokia Siemens Networks, Nokia | - |
R3‑081281 | Issues and Enhanced Framework for the Energy Saving Use Case | Nokia Siemens Networks, Nokia, | - |
R3‑081282 | Considerations on 36.902s Interference Reduction Use Case | Nokia Siemens Networks, Nokia | - |
R3‑081283 | HeNB registration and setup procedures | Nokia Siemens Networks, Nokia | - |
R3‑081284 | HeNB GW deployment analysis | Nokia Siemens Networks, Nokia | - |
R3‑081285 | Comparison of proposed methods for HeNBs architectures as described in TR R3.020 section 6.2.1.2 | Nokia Siemens Networks, Nokia | - |
R3‑081286 | Mobility Procedures for HeNB deployment scenarios | Nokia Siemens Networks, Nokia | - |
R3‑081287 | Data forwarding for Inter 3GPP-RAT HO | Nokia Siemens Networks, Nokia, | - |
R3‑081288 | Tunneling of 1xRTT RAND parameter in Uplink S1 CDMA2000 Tunneling message | Nokia Siemens Networks, Nokia | - |
R3‑081289 | On S1/X2 Setup procedure | Nokia Siemens Networks, Nokia, | - |
R3‑081290 | X2 Setup Update | Nokia Siemens Networks, Nokia | replaced by R3-081410 |
R3‑081291 | Framework for exchange of cell-level measurements on X2AP | Nokia Siemens Networks, Nokia, | - |
R3‑081292 | Load Balancing | Nokia Siemens Networks, Nokia | - |
R3‑081293 | ICIC Reporting Capability in X2 Setup | Nokia Siemens Networks, Nokia, | - |
R3‑081294 | Criticality Diagnostics | Nokia Siemens Networks, Nokia | agreed for 36.423 |
R3‑081295 | X2AP Clean-up | Nokia Siemens Networks, Nokia, | agreed for 36.423 |
R3‑081296 | Load Balancing mechanism for the S1 interface | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑081297 | S1 Setup update procedures | Nokia Siemens Networks, Nokia, Vodafone e | - |
R3‑081298 | S1 Setup/S1 Setup update procedures and Load Balancing | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑081299 | Aspects for MME pool configuration updates and eNB Introduction | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑081300 | MME pool configuration | Nokia Siemens Networks, Nokia, Vodafone | goes in 1507 |
R3‑081301 | Overload handling on the S1 interface | Nokia Siemens Networks, Nokia, Vodafone e | - |
R3‑081302 | Overload handling on the S1 interface | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑081303 | Overload handling on the S1 interface | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑081304 | S1 Setup Update procedure | Nokia Siemens Networks, Nokia, Vodafone | - |
R3‑081305 | NAS PDU IE in Initial Context Setup Response message | Nokia Siemens Networks, Nokia | ongoing in RAN2 |
R3‑081306 | Signalling of eNB Security capabilities | Nokia Siemens Networks, Nokia | - |
R3‑081307 | Signalling of eNB Security capabilities | Nokia Siemens Networks, Nokia | - |
R3‑081308 | Criticality diagnostics | Nokia Siemens Networks, Nokia | agreed for 36.413 |
R3‑081309 | Clarification for RAB Assignment procedure usage with IP beaer modification | Nokia Siemens Networks, Nokia | - |
R3‑081310 | Access control for IDLE and ACTIVE mode | Nokia Siemens Networks, Nokia | - |
R3‑081311 | Access control for IDLE and ACTIVE mode | Nokia Siemens Networks, Nokia | - |
R3‑081312 | Mobility active and idle | Nokia Siemens Networks, Nokia | - |
R3‑081313 | Mobility active and idle | Nokia Siemens Networks, Nokia | - |
R3‑081314 | Attempt to Approach 3G HNB topic by a Reference Architecture | Nokia Siemens Networks, Nokia | - |
R3‑081315 | Attempt to Approach 3G HNB topic by a Reference Architecture | Nokia Siemens Networks, Nokia | - |
R3‑081316 | 3G HNB Registration | Nokia Siemens Networks, Nokia | - |
R3‑081317 | 3G HNB Registration | Nokia Siemens Networks, Nokia | - |
R3‑081318 | Support for Legacy UTRAN functionsNokia Siemens Networks, Nokia | Nokia Siemens Networks, Nokia | - |
R3‑081319 | Support for Legacy UTRAN functionsNokia Siemens Networks, Nokia | Nokia Siemens Networks, Nokia | - |
R3‑081320 | Support of 3G HNB | Nokia Siemens Networks, Nokia | - |
R3‑081321 | Support of 3G HNB | Nokia Siemens Networks, Nokia | - |
R3‑081322 | HeNB and CSG addressing | Nokia Siemens Networks, Nokia s Networks, Nokia ns | - |
R3‑081323 | Addressing within E-UTRAN | Nokia Siemens Networks, Nokia | - |
R3‑081324 | GANSS Corrections | Qualcomm Europe | - |
R3‑081325 | Handling Duplicate TNL Associations | Fujitsu, Nortel | - |
R3‑081326 | Abnormal condition for S1 Setup: Handling Duplicate TNL Associations over S1 | Fujitsu, Nortel | - |
R3‑081327 | Abnormal condition for X2 Setup: Handling Duplicate TNL Associations over X2 | Fujitsu, Nortel | - |
R3‑081328 | Handling Duplicate TNL associations over X2 | Fujitsu, Nortel | - |
R3‑081329 | X2 Setup: Handling Duplicate TNL associations over X2 | Fujitsu, Nortel | - |
R3‑081330 | SCTP Restart Mechanism Impact on S1 Interface | Fujitsu | - |
R3‑081331 | S1 Setup after SCTP Restart | Fujitsu | tbc |
R3‑081332 | Control and handling of Data Forwarding | Nokia Siemens Networks, Nokia | - |
R3‑081333 | Control and handling of Data Forwarding | Nokia Siemens Networks, Nokia | tbc |
R3‑081334 | Abnormal condition for handover preparation | Nokia Siemens Networks, Nokia | replaced by 1559 |
R3‑081335 | TR R3.020 v0.5.0 | Nokia Siemens Networks, Nokia | R3.020 |
R3‑081336 | Discussion on GAN based HNB architecture | Samsung | - |
R3‑081337 | 3G HNB : Protocol Stack Description based on functions | Samsung | - |
R3‑081338 | Add Additional Time Slot LCR IE in common measuement messages | Ericsson, ZTE, Td-Tech, CATT | not agreed this meeting, tbc next meeting |
R3‑081339 | Add Additional Time Slot LCR IE in common measuement messages | Ericsson, ZTE, Td-Tech, CATT | not agreed this meeting, tbc next meeting |
R3‑081340 | ASN.1 and tabular misalignment | Ericsson | - |
R3‑081341 | ASN.1 and tabular misalignment | Ericsson | - |
R3‑081342 | ASN.1 and tabular misalignment | Ericsson | - |
R3‑081343 | ASN.1 and tabular misalignment | Ericsson | - |
R3‑081344 | Indication if octet aligned or non aligned table should be used when 64QAM is not used | Ericsson | - |
R3‑081345 | Indication if octet aligned or non aligned table should be used when 64QAM is not used | Ericsson | - |
R3‑081346 | Indication if octet aligned or non aligned table should be used when 64QAM is not used | Ericsson | - |
R3‑081347 | Indication if octet aligned or non aligned table should be used when 64QAM is not used | Ericsson | - |
R3‑081348 | Additional UE reporting in ANR | Ericsson | - |
R3‑081349 | Self configuration of S1 HO information | Ericsson | - |
R3‑081350 | Transparent HeNB Gateway considering the S1AP-ID-s | Ericsson, Huawei | - |
R3‑081351 | Transparent HeNB Gateway considering the S1 user plane transport | Ericsson, Huawei | - |
R3‑081352 | S1-handover routing with auto configuration for HeNB-s | Ericsson | - |
R3‑081353 | Discussion on ETWS S1-based network architecture option | Ericsson | - |
R3‑081354 | Dynamic configuration of the X2 interface | Ericsson | - |
R3‑081355 | Alignment of X2 Release Resource name to S1 naming | Ericsson | R3-081158 Specific cause value for X2 handover preparation failure (Huawei) agreed for 36.300 |
R3‑081356 | Alignment of X2 Release Resource name to S1 naming | Ericsson | agreed for 36.423 |
R3‑081357 | X2 application data update | Ericsson | - |
R3‑081358 | X2 Update procedure | Ericsson, Huawei | - |
R3‑081359 | Addition of missing statement on the order of bits in bitstrings | Ericsson | - |
R3‑081360 | Correction of the procedure text in order to avoid IOT issues | Ericsson | - |
R3‑081361 | Served Cell Information alignment with RRC 36.331 | Ericsson | - |
R3‑081362 | Define format for TLA signalled in S1AP messages | Ericsson | - |
R3‑081363 | Define format for TLA signalled in X2AP messages | Ericsson | - |
R3‑081364 | Addition of missing cause values | Ericsson | - |
R3‑081365 | Clarification of specification principles in order to avoid IOT issues | Ericsson | - |
R3‑081366 | Clarification of specification principles in order to avoid IOT issues | Ericsson | - |
R3‑081367 | Correct reference of TLA format | Ericsson | agreed for 36.413 |
R3‑081368 | Correct reference of TLA format | Ericsson | agreed for 36.423 |
R3‑081369 | eNB Global ID range | Ericsson | - |
R3‑081370 | eNB Global ID range | Ericsson | - |
R3‑081371 | AMBR corrections | Ericsson | agreed for 36.413 |
R3‑081372 | Handover restriction list signalling | Ericsson | - |
R3‑081373 | HO restriction info in Path Switch | Ericsson | - |
R3‑081374 | IDs in S1 HO | Ericsson, TeliaSonera | - |
R3‑081375 | Content for Target eNB to Source eNB Transparent Container | Ericsson | agreed for 36.413 |
R3‑081376 | Switching the UL Tunnel Endpoint in the Path Switch Request procedure | Ericsson | agreed for 36.413 |
R3‑081377 | eNB UE S1 AP ID in handover request | Ericsson | agreed for 36.413 |
R3‑081378 | Criticality Diagnostics clean-up | Ericsson | withdrawn in favour of 1308 |
R3‑081379 | S1 update | Ericsson | - |
R3‑081380 | S1 application data update | Ericsson, Huawei | - |
R3‑081381 | CGI and eNB ID coding and size | Ericsson | - |
R3‑081382 | EUTRAN Cell Global Identifier coding | Ericsson, TeliaSonera | - |
R3‑081383 | Clarification on the Download of UE Capability Information from the EPC | Ericsson, Huawe | - |
R3‑081384 | Transport Layer Address coding | Ericsson | - |
R3‑081385 | Max Transport Block Size limit for EUL in CELL_FACH Ues | Ericsson | - |
R3‑081386 | Handling of E-RNTI and H-RNTI for E-DCH in CELL_FACH | Ericsson | - |
R3‑081387 | Indication of Required EUL uplink resources from Node B for GBR Radio Bearers | Ericsson | - |
R3‑081388 | Indication of required EUL uplink resources from Node B for GBR Radio Bearers | Ericsson | - |
R3‑081389 | Indication of UE 3GPP Relase to NodeB | Ericsson | - |
R3‑081390 | Indication of UE 3GPP Relase to NodeB | Ericsson | - |
R3‑081391 | Correction of figure 6.4.1 | Ericsson | - |
R3‑081392 | Signalling of eNB Security capabilities | Nokia Siemens Networks, Nokia | linked to 1307 |
R3‑081393 | The discussion and proposal on the S1 Setup/Update | NEC, Alcatel-Lucent | - |
R3‑081394 | Changing S1 Setup procedure | NEC | - |
R3‑081395 | Introducing S1 update procedures | NEC, Alcatel-Lucent | - |
R3‑081396 | The discussion and proposal on the X2 Setup/Update | NEC | - |
R3‑081397 | Changing X2 Setup procedur | NEC | - |
R3‑081398 | Introducing X2 update procedure | NEC | - |
R3‑081399 | Inclusion of eNB capability information in the S1 Setup procedure | NEC | - |
R3‑081400 | Adding eNB Capability Information | NEC | - |
R3‑081401 | Release of MBMS Signalling Connection | NEC | - |
R3‑081402 | Correction of the Release of MBMS Signalling Connection | NEC | - |
R3‑081403 | Load Balancing procedure for X2 interface | NEC | - |
R3‑081404 | Load Balancing procedure for X2 interface | NEC | - |
R3‑081405 | Signaling of cell BW and frequency over X2 interface | NEC | - |
R3‑081406 | Signaling of cell BW and frequency over X2 interface | NEC | tbc |
R3‑081407 | Fast CS service redirection for LTE | NEC | - |
R3‑081408 | IRAT ANR enhancement | NEC | - |
R3‑081409 | IRAT ANR enhancement | NEC | - |
R3‑081410 | X2 Setup Update | Nokia Siemens Networks, Nokia | - |
R3‑081411 | Hierarchy S1 Setup, Setup Update and Reset | Nokia Siemens Networks, Nokia, Vodafone e | - |
R3‑081412 | Paging load reduction in asynchronous cells | Motorola | - |
R3‑081413 | Over-the-air paging load reduction | Motorola | to be continued on email reflector |
R3‑081414 | Exchange of eUTRAN neighbour information | Motorola | - |
R3‑081415 | Exchange of eUTRAN neighbours in X2 SETUP | Motorola | tbc |
R3‑081416 | X2 shutdown | Motorola | - |
R3‑081417 | Recap of load balancing discussion | Motorola | - |
R3‑081418 | Protocol Stacks for 3GHNB access and addressing aspects | Nokia Siemens Networks, Nokia | - |
R3‑081419 | Protocol Stacks for 3GHNB access and addressing aspects | Nokia Siemens Networks, Nokia | - |
R3‑081420 | Power Control Gap IE handling | Alcatel-Lucent | linked to R3-081198 |
R3‑081421 | Load balancing with ping pong avoidance support in Active and Idle mode | NTT DoCoMo | - |
R3‑081422 | Iu Release Procedure for Enhanced Relocation | Nokia Siemens Networks, Nokia | R3.021 |
R3‑081423 | Identified issue for NAS Handling | Nokia Siemens Networks, Nokia | R3.021 |
R3‑081424 | On Resource Allocation | Nokia Siemens Networks, Nokia | - |
R3‑081425 | Inter-Cell Interference Co-ordination SON Use Case | Alcatel-Lucent, Telecom Italia, CMCC, Orange, Telefonica, T-Mobile, Samsung, Huawei, ZTE | 36.902 |
R3‑081426 | Handling of C-Plane in HeNB GW | Nokia Siemens Networks | - |
R3‑081427 | Handling of U-Plane in HeNB GW | Nokia Siemens Networks | - |
R3‑081428 | Correction on "Enhancements to Macro Diversity & Cell Interference Control" | Huawei, Nokia, Nokia Siemens Network | - |
R3‑081429 | RL Parameter Update for E-DCH FDD DL Control Channel Information | Nokia Siemens Networks, Nokia | - |
R3‑081430 | RL Parameter Update for E-DCH FDD DL Control Channel Information | Nokia Siemens Networks, Nokia | - |
R3‑081431 | RL Parameter Update for E-DCH FDD DL Control Channel Information | Nokia Siemens Networks, Nokia | - |
R3‑081432 | RL Parameter Update for E-DCH FDD DL Control Channel Information | Nokia Siemens Networks, Nokia | - |
R3‑081433 | Load Balancing | Nokia Siemens Networks, Nokia | - |
R3‑081434 | Clarification of specification principles in order to avoid IOT issues | Ericsson,Huawei | - |
R3‑081435 | Clarification of specification principles in order to avoid IOT issues | Ericsson, Huawei | - |
R3‑081436 | Revised report of RAN3#59bis, Shenzhen, China | MCC | - |
R3‑081437 | Mechanism for Scheduling Information transmission on MAC-e PDU alone for 1.28 Mcps TDD in EUL | CATT | - |
R3‑081438 | Mechanism for Scheduling Information transmission on MAC-e PDU alone for 1.28 Mcps TDD in EUL | CATT | - |
R3‑081439 | Mechanism for Scheduling Information transmission on MAC-e PDU alone for 1.28 Mcps TDD in EUL | CATT | - |
R3‑081440 | Mechanism for Scheduling Information transmission on MAC-e PDU alone for 1.28 Mcps TDD in EUL | CATT | - |
R3‑081441 | Modification of E-HICH Time Offset configuration for LCR TDD | ZTE,CATT,TD TECH | - |
R3‑081442 | Modification of E-HICH Time Offset configuration for LCR TDD | ZTE,CATT,TD TECH | - |
R3‑081443 | Extended power control gap for E-PUCH in LCR TDD | TD Tech, CATT, ZTE | - |
R3‑081444 | Extended power control gap for E-PUCH in LCR TDD | TD Tech, CATT, ZTE | - |
R3‑081445 | Extended power control gap for E-PUCH in LCR TDD | TD Tech, CATT, ZTE | - |
R3‑081446 | Extended power control gap for E-PUCH in LCR TDD | TD Tech, CATT, ZTE | - |
R3‑081447 | Correction of Maximum MAC-d/c PDU Length IE definition for frame protocol type 2 | Alcatel-Lucent | rejected for now , tbc next meeting |
R3‑081448 | Correction of Maximum MAC-d PDU Length Type 2 IE definition for frame protocol type 2 | Alcatel-Lucent | rejected for now , tbc next meeting |
R3‑081449 | Support of octet aligned HS-DSCH transport block sizes for non-64QAM | Alcatel-Lucent, Ericsson | - |
R3‑081450 | Support of octet aligned HS-DSCH transport block sizes for non-64QAM | Alcatel-Lucent, Ericsson | - |
R3‑081451 | Support of octet aligned HS-DSCH transport block sizes for non-64QAM | Alcatel-Lucent, Ericsson | - |
R3‑081452 | Support of octet aligned HS-DSCH transport block sizes for non-64QAM | Alcatel-Lucent, Ericsson | - |
R3‑081453 | Adding the S-TMSI into the INITIAL UE MESSAGE | CATT | - |
R3‑081454 | Skeleton of TR36.913 "Requirements for LTE-Advanced" | LTE-Advanced rapporteur (NTT DoCoMo) | - |
R3‑081455 | Operator's views on requirements for LTE-Advanced | NTT DoCoMo, AT&T, CMCC, Orange, Telecom Italia, TeliaSonera, T-Mobile and Vodafone | - |
R3‑081456 | Use of UL DPDCH Indicator For E-DCH Operation IE for unsynchronised RL reconfiguration | Acatel-Lucent | email check#05 |
R3‑081457 | Use of UL DPDCH Indicator For E-DCH Operation IE for unsynchronised RL reconfiguration | Acatel-Lucent | email check#05 |
R3‑081458 | Use of UL DPDCH Indicator For E-DCH Operation IE for unsynchronised RL reconfiguration | Acatel-Lucent | email check#05 |
R3‑081459 | Use of UL DPDCH Indicator For E-DCH Operation IE for unsynchronised RL reconfiguration | Acatel-Lucent | email check#05 |
R3‑081460 | Use of UL DPDCH Indicator For E-DCH Operation IE for unsynchronised RL reconfiguration | Acatel-Lucent | email check#05 |
R3‑081461 | Use of UL DPDCH Indicator For E-DCH Operation IE for unsynchronised RL reconfiguration | Acatel-Lucent | email check#05 |
R3‑081462 | X2 NRL self-configuration | Ericsson | - |
R3‑081463 | Clarification on Transport Bearer Not Requested Indicator | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑081464 | Clarification on Transport Bearer Not Requested Indicator | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑081465 | Clarification on Transport Bearer Not Requested Indicator | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑081466 | Clarification on Transport Bearer Not Requested Indicator | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑081467 | Addressing within E-UTRAN | Nokia Siemens Networks, Nokia | - |
R3‑081468 | Support of 3G HNB | Nokia Siemens Networks, Nokia | - |
R3‑081469 | LS on Data forwarding for Inter 3GPP-RAT HO from E-UTRAN to UMTS/GERAN | Nokia Siemens Networks | - |
R3‑081470 | LS on the AP ID Uniqueness | Huawei | - |
R3‑081471 | LS on Subscriber type Transfer over S1 and X2 | Vodafone | - |
R3‑081472 | Tunneling of 1xRTT RAND parameter in Uplink S1 CDMA2000 Tunneling message | Nokia Siemens Networks, Nokia, Alcatel-Lucent, Ericsson, Motorola, Nortel, Verizon Wireless | - |
R3‑081473 | Introduction of cause values for X2 handover | Alcatel-Lucent | agreed for 36.423 |
R3‑081474 | Introduction of new handover cause values over X2 | Alcatel-Lucent | - |
R3‑081475 | Introduction of new handover cause values over S1 | Alcatel-Lucent | agreed for 36.413 |
R3‑081476 | Addition of new causes for consistency | Nortel, Alcatel-Lucent | agreed for 36.423 |
R3‑081477 | Handover Cancellation timing | 'NTT DoCoMo, NEC, Alcatel-Lucent' | - |
R3‑081478 | Handover Cancellation timing | 'NTT DoCoMo, NEC | tbc |
R3‑081479 | Further consideration on architecture for MBMS over HSPA+ | ZTE | - |
R3‑081480 | Introduction of Enhanced Relocation | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑081481 | Introduction of Enhanced Relocation | Nokia Siemens Networks, Nokia, Huawei | - |
R3‑081482 | GTP-PDU Impact for Improved GGSN | Nokia Siemens Networks, Nokia | - |
R3‑081483 | Problem on EDCH code Reconfiguration | Nokia Siemens Networks | - |
R3‑081484 | Interaction of Bearer Release and Handover procedures | Alcatel-Lucent | agreed for 36.413 |
R3‑081485 | Adding IEs in the INITIAL UE MESSAGE message | Huawei | agreed for 36.413 |
R3‑081486 | Management of the S-TMSI | Alcatel-Lucent | agreed for 36.413 |
R3‑081487 | LS on Handover Restriction List signalling | Ericsson | - |
R3‑081488 | HO restriction info in Path Switch | Ericsson | agreed for 36.413 |
R3‑081489 | Introduction of trace activation during S1 handover | CATT | agreed for 36.413 |
R3‑081490 | Reply LS on retransmission of UL and DL NAS message during inter-eNB handovers (C1-081987 reply LS for UL NAS Source: CT1, To: TSG RAN WG2, Cc: TSG RAN WG3) | CT1 | - |
R3‑081491 | LS on “Direct Data Forwarding for Inter 3GPP RAT Handover” (C4-081302 Source: CT4, To: TSG RAN WG3,TSG SA WG2, Cc: ) | CT4 | - |
R3‑081492 | LS on RAN3 requirements for GTPv2 (C4-081303_LS_RAN3_PDCP Source: CT4, To: TSG RAN WG3, Cc: ) | CT4 | - |
R3‑081493 | Addition of Location reporting procedure (36.300) | Huawei, NTT DoCoMo | - |
R3‑081494 | Addition of Location Reporting Procedure (CR 36.413) | Huawei, NTT DoCoMo | agreed for 36.413 |
R3‑081495 | Reply LS on the necessity of Location Reporting procedure in S1 | NTT DoCoMo | - |
R3‑081496 | Response LS on RAN3 requirements for GTPv2 | Ericsson | - |
R3‑081497 | CR for NAS Non Delivery Indication trigger update | Samsung | agreed for 36.413 |
R3‑081498 | - | - | - |
R3‑081499 | Abnormal Condition for S1 Setup | Nortel | agreed for 36.413 |
R3‑081500 | S1 Setup/S1 Setup update procedures and Load Balancing | Nokia Siemens Networks, Nokia, Vodafone | agreed for 36.300 |
R3‑081501 | LS on End Marker (C4-081314_LS_RAN3_End_Marker Source: CT4, To: TSG RAN WG3, Cc: ) | CT4 | - |
R3‑081502 | LS on “Changes to the format of TMGI” (C4-081359 Source: CT4, To: CT3,TSG RAN WG3, Cc: TSG RAN WG2,CT1) | CT4 | - |
R3‑081503 | Mechanism for Scheduling Information transmission on MAC-e PDU alone for 1.28 Mcps TDD in EUL | CATT | - |
R3‑081504 | Mechanism for Scheduling Information transmission on MAC-e PDU alone for 1.28 Mcps TDD in EUL | CATT | - |
R3‑081505 | Mechanism for Scheduling Information transmission on MAC-e PDU alone for 1.28 Mcps TDD in EUL | CATT | - |
R3‑081506 | Mechanism for Scheduling Information transmission on MAC-e PDU alone for 1.28 Mcps TDD in EUL | CATT | - |
R3‑081507 | Introducing S1 update procedures | NEC, Alcatel-Lucent | agreed for 36.413 |
R3‑081508 | Relation between S1 Setup and Reset procedures | Alcatel-Lucent, NEC | agreed for 36.413 |
R3‑081509 | RL Parameter Update for E-DCH FDD DL Control Channel Information | Nokia Siemens Networks, Nokia | - |
R3‑081510 | RL Parameter Update for E-DCH FDD DL Control Channel Information | Nokia Siemens Networks, Nokia | - |
R3‑081511 | RL Parameter Update for E-DCH FDD DL Control Channel Information | Nokia Siemens Networks, Nokia | - |
R3‑081512 | RL Parameter Update for E-DCH FDD DL Control Channel Information | Nokia Siemens Networks, Nokia | - |
R3‑081513 | LS on Intra-cell handover for MME load rebalancing | Samsung | - |
R3‑081514 | Tunneling of 1xRTT RAND parameter in Uplink S1 CDMA2000 Tunneling message | Nokia Siemens Networks, Nokia, Alcatel-Lucent, Ericsson, Motorola, Nortel, Verizon Wireless | agreed for 36.413 |
R3‑081515 | eGTP draft reference for S1 Data Transport | Nortel | - |
R3‑081516 | eGTP draft reference for X2 Data Transport | Nortel | - |
R3‑081517 | Correction of tunnel endpoints | Alcatel-Lucent | agreed for 36.423 |
R3‑081518 | Correction of the QoS | Alcatel-Lucent | agreed for 36.423 |
R3‑081519 | LS on NodeB measurement to report common E-DCH Resource Usage (R2-082797 Source: TSG RAN WG2, To: TSG RAN WG3, Cc: ) | TSG RAN WG2 | - |
R3‑081520 | Load Balancing procedure for X2 interface | NEC | email check #09 |
R3‑081521 | Support of 3G HNB | Nokia Siemens Networks, Nokia | - |
R3‑081522 | Support of 3G HNB | Kineto , Alcatel-Lucent | - |
R3‑081523 | Support of 3G HNB | Nokia Siemens Networks, Nokia | - |
R3‑081524 | Agreements of 1521 for TR R3.020 | Nokia Siemens Networks, Nokia | - |
R3‑081525 | Agreements of 1521 for TR R3.020 | Nokia Siemens Networks, Nokia, Ericsson, Huawei, Kineto Wireless Inc, Alcatel-Lucent, Motorola, NEC | - |
R3‑081526 | Additional UE reporting in ANR | Ericsson | 36.300 |
R3‑081527 | Draft LS on E-UTRAN identifiers | Nokia Siemens Networks | - |
R3‑081528 | Introduction of new handover cause values over X2 | Alcatel-Lucent, ZTE, China Mobile | agreed for 36.423 |
R3‑081529 | IRAT ANR enhancement | NEC | agreed from RAN3, not for big CR |
R3‑081530 | Inter-Cell Interference Co-ordination SON Use Case | Alcatel-Lucent, Telecom Italia, CMCC, Orange, Telefonica, T-Mobile, Samsung, Huawei, ZTE, Nortel | 36.902 |
R3‑081531 | Response LS on RAN3 requirements for GTPv2 | Ericsson | - |
R3‑081532 | Response LS on RAN3 requirements for GTPv2 | RAN3 | - |
R3‑081533 | Draft LS on E-UTRAN identifiers | Nokia Siemens Networks | - |
R3‑081534 | LS on E-UTRAN identifiers | RAN3 | - |
R3‑081535 | LS on Data forwarding for Inter 3GPP-RAT HO from E-UTRAN to UMTS/GERAN | Nokia Siemens Networks | - |
R3‑081536 | GANSS Corrections | Qualcomm Europe, Alcatel-Lucent | - |
R3‑081537 | GANSS Corrections | Qualcomm Europe, Alcatel-Lucent | - |
R3‑081538 | GANSS Corrections | Qualcomm Europe, Alcatel-Lucent | - |
R3‑081539 | GANSS Corrections | Qualcomm Europe, Alcatel-Lucent | - |
R3‑081540 | GANSS Corrections | Qualcomm Europe, Alcatel-Lucent | - |
R3‑081541 | Clarification of specification principles in order to avoid IOT issues | Ericsson,Huawei | - |
R3‑081542 | Clarification of specification principles in order to avoid IOT issues | Ericsson, Huawei | - |
R3‑081543 | LS on Enhancements for SRNS Relocation | Nokia Siemens Networks | - |
R3‑081544 | Addition of missing cause values | Ericsson | agreed for 36.413 |
R3‑081545 | LS on RAN3 Status on Enhanced Uplink in Cell_FACH in FDD | Nokia Siemens Networks | - |
R3‑081546 | Reply LS on reply LS on Paging Permission with Access Control (PPAC) | NTT DoCoMo | - |
R3‑081547 | Rejection causes over X2 | Alcatel-Lucent | agreed for 36.423 |
R3‑081548 | introduction of feature indicator | Ericsson | - |
R3‑081549 | introduction of feature indicator | Ericsson | - |
R3‑081550 | Correction on "Enhancements to Macro Diversity & Cell Interference Control" | Huawei, Nokia, Nokia Siemens Networks | email discussion:#04 |
R3‑081551 | Correction on "Enhancements to Macro Diversity & Cell Interference Control" | Huawei, Nokia, Nokia Siemens Networks | email discussion:#04 |
R3‑081552 | Further consideration on architecture for MBMS over HSPA+ | ZTE | email check#10 |
R3‑081553 | transport efficiency | Huawei | - |
R3‑081554 | Impact of inter eNB handover on location reporting procedure | NTT DoCoMo | email check #07 |
R3‑081555 | notes on the discussion of handover cancellation timing | NTT DoCoMo | - |
R3‑081556 | clarification of discussion on interface options for ETWS | NTT DoCoMo | - |
R3‑081557 | LS on Data forwarding for Inter 3GPP-RAT HO from E-UTRAN to UMTS/GERAN | Nokia Siemens Networks | - |
R3‑081558 | X2 Update procedure | Ericsson, Huawei | agreed for 36.423 |
R3‑081559 | Direct Forwarding Path Availability IE | Nokia Siemens Networks, Nokia | agreed for 36.413 |
R3‑081560 | GANSS Corrections | Qualcomm Europe, Alcatel-Lucent | - |
R3‑081561 | GANSS Corrections | Qualcomm Europe, Alcatel-Lucent | - |
R3‑081562 | GANSS Corrections | Qualcomm Europe, Alcatel-Lucent | - |
R3‑081563 | GANSS Corrections | Qualcomm Europe, Alcatel-Lucent | - |
R3‑081564 | Addition of Location reporting procedure (36.300) | Huawei, NTT DoCoMo | agreed for 36.300 |
R3‑081565 | LS on Data forwarding for Inter 3GPP-RAT HO from E-UTRAN to UMTS/GERAN | Nokia Siemens Networks | - |
R3‑081566 | LS on the AP ID Uniqueness | Huawei | - |
R3‑081567 | LS on the AP ID Uniqueness | RAN3 | - |
R3‑081568 | TR R3.021 v400 | Nokia Siemens Networks, Nokia | email check #15 |
R3‑081569 | S1 setup | Nokia Siemens Networks, Nokia | agreed for 36.300 |
R3‑081570 | Support of 3G HNB | Nokia Siemens Networks, Nokia, Ericsson, Huawei, Kineto, NEC, Motorola, Alcatel-Lucent, Vodafone, Samsung, ipaccess | - |
R3‑081571 | LS to RAN4 on RAN3 agreed CR to TR25.820 | RAN3 | - |
R3‑081572 | LS on Handover Restriction List signalling | Ericsson | - |
R3‑081573 | LS on Handover Restriction List signalling | RAN3 | - |
R3‑081574 | Handover Cancellation timing | 'NTT DoCoMo, NEC, Alcatel-Lucent' | agreed for 36.413 |
R3‑081575 | LS on Data forwarding for Inter 3GPP-RAT HO from E-UTRAN to UMTS/GERAN | Nokia Siemens Networks | - |
R3‑081576 | LS on Data forwarding for Inter 3GPP-RAT HO from E-UTRAN to UMTS/GERAN | RAN3 | - |
R3‑081577 | LS on MME pool configuration | Nokia Siemens Networks | - |
R3‑081578 | LS on MME pool configuration | RAN3 | - |
R3‑081579 | LS on Intra-cell handover for MME load rebalancing | Samsung | - |
R3‑081580 | LS on Intra-cell handover for MME load rebalancing | RAN3 | - |
R3‑081581 | Reply LS on the necessity of Location Reporting procedure in S1 | NTT DoCoMo | - |
R3‑081582 | Reply LS on the necessity of Location Reporting procedure in S1 | RAN3 | - |
R3‑081583 | LS onIRAT ANR | NEC | email check#08 |
R3‑081584 | LS on Enhancements for SRNS Relocation | Nokia Siemens Networks | - |
R3‑081585 | LS on Enhancements for SRNS Relocation | Nokia Siemens Networks | - |
R3‑081586 | LS on RAN3 Status on Enhanced Uplink in Cell_FACH in FDD | RAN3 | - |
R3‑081587 | Reply LS on reply LS on Paging Permission with Access Control (PPAC) | RAN3 | - |
R3‑081588 | Support of 3G HNB | Nokia Siemens Networks, Nokia, Ericsson, Huawei, Kineto, NEC, Motorola, Alcatel-Lucent, Vodafone, Samsung, ipaccess | agreed for 25.820 |
R3‑081589 | RAN3 agreed changes for TS 36.401 | NEC | big CR |
R3‑081590 | RAN3 agreed changes for TS 36.413 | Nokia Siemens Networks | big CR |
R3‑081591 | RAN3 agreed changes for TS 36.423 | Ericsson | big CR |
R3‑081592 | RAN3 agreed changes to TS 36.300 | Ericsson | big CR |
R3‑081593 | Load Balancing procedure for X2 interface | NEC | agreed for 36.423 |
R3‑081594 | LS on Load balancing signalling on QCI | Ericsson | - |
R3‑081595 | R3.022 v0.3.0 | Nokia Siemens Networks, Nokia | R3.022 |
R3‑081596 | TR R3.020 v0.6.0 | Nokia Siemens Networks, Nokia | R3.020 |
R3‑081597 | Use of UL DPDCH Indicator For E-DCH Operation IE for unsynchronised RL reconfiguration | Acatel-Lucent | email check#05 |
R3‑081598 | Use of UL DPDCH Indicator For E-DCH Operation IE for unsynchronised RL reconfiguration | Acatel-Lucent | email check#05 |
R3‑081599 | Use of UL DPDCH Indicator For E-DCH Operation IE for unsynchronised RL reconfiguration | Acatel-Lucent | email check#05 |
R3‑081600 | Use of UL DPDCH Indicator For E-DCH Operation IE for unsynchronised RL reconfiguration | Acatel-Lucent | email check#05 |
R3‑081601 | Use of UL DPDCH Indicator For E-DCH Operation IE for unsynchronised RL reconfiguration | Acatel-Lucent | email check#05 |
R3‑081602 | Use of UL DPDCH Indicator For E-DCH Operation IE for unsynchronised RL reconfiguration | Acatel-Lucent | email check#05 |
R3‑081603 | Impact of inter eNB handover on location reporting procedure | NTT DoCoMo | agreed for 36.423 |
R3‑081604 | Clarification of specification principles in order to avoid IOT issues | Ericsson,Huawei | agreed for 36.423 |
R3‑081605 | Clarification of specification principles in order to avoid IOT issues | Ericsson, Huawei | agreed for 36.413 |
R3‑081606 | LS onIRAT ANR | RAN3 | email check#08 |
R3‑081607 | LS on Load balancing signalling on QCI | RAN3 | - |
R3‑081608 | Example Signalling Procedure for Centric MBMS Architecture | Huawei | - |
R3‑081609 | Synchronisation scheme for Improved GGSN | Nokia Siemens Networks, Nokia | - |
page generated from database: 2024-09-26 11:02:35