The 5G Standard

3GPP TDocs (written contributions) at meeting

Meeting: R3-15 - 2000-08-21 to 2000-08-25, BERLIN

meeting id: R3-15 (click id for more info on this meeting)

Click on the Tdoc to open its file.

TDoc Title Source Remarks
R3‑001999 - - -
R3‑002000 - - -
R3‑002001 - - -
R3‑002002 - - -
R3‑002003 - - -
R3‑002004 - - -
R3‑002005 - - -
R3‑002006 - - -
R3‑002007 - - -
R3‑002008 - - -
R3‑002009 - - -
R3‑002010 - - -
R3‑002011 - - -
R3‑002012 - - -
R3‑002013 - - -
R3‑002014 - - -
R3‑002015 - - -
R3‑002016 - - -
R3‑002017 - - -
R3‑002018 - - -
R3‑002019 - - -
R3‑002021 - - -
R3‑002022 - - -
R3‑002023 - - -
R3‑002024 - - -
R3‑002025 - - -
R3‑002026 - - -
R3‑002027 - - -
R3‑002028 - - -
R3‑002029 - - -
R3‑002030 Clarification for Multi-DPCH cases - -
R3‑002031 Clarification for Multi-DPCH cases - -
R3‑002032 - - -
R3‑002033 - - -
R3‑002034 - - -
R3‑002035 - - -
R3‑002036 DSCH Corrections - -
R3‑002037 - - -
R3‑002038 DSCH Corrections - -
R3‑002039 - - -
R3‑002040 - - -
R3‑002042 - - -
R3‑002044 - - -
R3‑002045 - - -
R3‑002046 - - -
R3‑002047 - - -
R3‑002048 - - -
R3‑002049 - - -
R3‑002050 Clarification on re-assignment of Iu-signalling connection after Reset Resource procedure - -
R3‑002051 Clarification on list of Iu signalling connection identifiers within RESET RESOURCE ACKNOWLEDGE message - -
R3‑002053 - - -
R3‑002054 - - -
R3‑002055 - - -
R3‑002056 - - -
R3‑002057 - - -
R3‑002058 - - -
R3‑002059 - - -
R3‑002060 - - -
R3‑002061 - - -
R3‑002062 - - -
R3‑002063 - - -
R3‑002064 - - -
R3‑002065 - - -
R3‑002066 - - -
R3‑002067 - - -
R3‑002068 - - -
R3‑002069 Remove Draft in the of the reference Q.2630.1 in 25.424 - -
R3‑002070 Remove Draft in the of the reference Q.2630.1 and Q.2150.2 in 25.426 - -
R3‑002071 Remove Draft in the of the reference Q.2630.1 and Q.2150.2 in 25.434 - -
R3‑002072 Cause value needed for relocation because of resource optimisation - -
R3‑002073 - - -
R3‑002074 - - -
R3‑002075 - - -
R3‑002076 - - -
R3‑002077 Need to disable Timing advance - -
R3‑002078 - - -
R3‑002079 - - -
R3‑002080 - - -
R3‑002081 - - -
R3‑002082 - - -
R3‑002084 Renaming of Timeslot ISCP - -
R3‑002085 Renaming of Timeslot ISCP - -
R3‑002086 - - -
R3‑002087 - - -
R3‑002088 Clarification to the RL Failure procedure - -
R3‑002089 - - -
R3‑002090 - - -
R3‑002091 - - -
R3‑002092 - - -
R3‑002093 - - -
R3‑002094 - - -
R3‑002095 - - -
R3‑002096 - - -
R3‑002097 - - -
R3‑002098 - - -
R3‑002099 - - -
R3‑002100 - - -
R3‑002101 - - -
R3‑002102 - - -
R3‑002103 - - -
R3‑002105 - - -
R3‑002106 - - -
R3‑002107 - - -
R3‑002108 - - -
R3‑002109 - - -
R3‑002110 - - -
R3‑002111 - - -
R3‑002112 - - -
R3‑002113 - - -
R3‑002117 - - -
R3‑002118 - - -
R3‑002119 - - -
R3‑002120 - - -
R3‑002121 - - -
R3‑002122 - - -
R3‑002123 - - -
R3‑002124 Introduction of DL Codes Not Supported cause value - -
R3‑002125 Introduction of DL Codes Not Supported cause value - -
R3‑002126 Principles for functional distribution between SRNC and CRNC - -
R3‑002127 - - -
R3‑002128 - - -
R3‑002129 - - -
R3‑002130 - - -
R3‑002131 - - -
R3‑002132 - - -
R3‑002133 - - -
R3‑002134 - - -
R3‑002136 - - -
R3‑002137 - - -
R3‑002138 - - -
R3‑002139 - - -
R3‑002140 - - -
R3‑002141 - - -
R3‑002142 - - -
R3‑002143 - - -
R3‑002144 - - -
R3‑002145 - - -
R3‑002146 - - -
R3‑002147 - - -
R3‑002148 - - -
R3‑002149 - - -
R3‑002150 - - -
R3‑002151 - - -
R3‑002152 - - -
R3‑002154 - - -
R3‑002155 - - -
R3‑002156 Correction in Common measurement report message for CPCH - -
R3‑002157 - - -
R3‑002158 - - -
R3‑002159 - - -
R3‑002160 - - -
R3‑002161 Overlapping CN Broadcast Areas - -
R3‑002162 - - -
R3‑002163 - - -
R3‑002164 Selection of user data PDU type - -
R3‑002165 Value range of PDU type - -
R3‑002166 Delivery of erroneous SDUs value alignment - -
R3‑002167 Updating RFC 1483 to RFC 2684 - -
R3‑002168 - - -
R3‑002169 - - -
R3‑002170 - - -
R3‑002171 - - -
R3‑002172 - - -
R3‑002173 Addition of reference for usages of MTP3b on Iu - -
R3‑002174 Additon of reference for usage of MTP3b on Iur - -
R3‑002175 - - -
R3‑002176 - - -
R3‑002177 - - -
R3‑002178 - - -
R3‑002179 Wrong implementation of CR123 in 25.413 v 3.2.0 - -
R3‑002180 Correcting the references in RANAP - -
R3‑002181 - - -
R3‑002182 - - -
R3‑002183 - - -
R3‑002184 RACH Transport format Correction in TDD - -
R3‑002185 BER at Uplink DTX for TDD - -
R3‑002186 BER at Uplink DTX for TDD - -
R3‑002187 - - -
R3‑002188 BER at Uplink DTX for TDD - -
R3‑002190 - - -
R3‑002191 - - -
R3‑002194 - - -
R3‑002195 - - -
R3‑002196 Clarification of usage of reporting objects in the RL restoration procedure - -
R3‑002197 - - -
R3‑002198 Questions on Behaviour in the “forward handover” scenario without an Iur in Release ‘99 R3 -
R3‑002199 - - -
R3‑002200 - - -
R3‑002201 Correction of timing and message name - -
R3‑002202 - - -
R3‑002203 - - -
R3‑002204 Limited power increase chapter - -
R3‑002205 Limited power increase chapter - -
R3‑002206 DSCH Corrections - -
R3‑002207 Correction of UL-FP mode and Measurement filter coefficient ranges in tabular format - -
R3‑002208 Measurement alignment - -
R3‑002209 Measurement alignment - -
R3‑002210 Alignment of DPCH parameters with WG1/WG2 in TDD - -
R3‑002211 Alignment of DPCH parameters with WG1/WG2 in TDD - -
R3‑002212 - - -
R3‑002213 Measurement Grouping in the DRNC - -
R3‑002214 - - -
R3‑002215 Resource status indication clarification - -
R3‑002216 - - -
R3‑002217 - - -
R3‑002218 Iub Admission Control - -
R3‑002219 - - -
R3‑002220 - - -
r3‑002221 - - -
R3‑002222 Reference between unsuccessful Location Report and Location Reporting Control - -
R3‑002223 Correction of SAPI values in RANAP ASN.1 code - -
R3‑002224 - - -
R3‑002225 - - -
R3‑002226 - - -
R3‑002227 Remove Unnecessary use of the ProtocolIE-Container - -
R3‑002228 BER at Uplink DTX for TDD - -
R3‑002229 Correction to Burst Type IE and Midamble Shift IE in TDD messages - -
R3‑002230 Correction of Burst Type IE and Midamble Shift IE in TDD messages - -
R3‑002231 Correction to FDD DL Channelisation Code Number IE definition - -
R3‑002232 Correction to FDD DL Channelisation Code Number IE definition - -
R3‑002233 - - -
R3‑002234 Correction to Compressed Mode - -
R3‑002235 Introduction of SRNC-Id in the RL SETUP REQUEST Message - -
R3‑002236 Missing Choice Tag in the RL RECONFIGURATION FAILURE Message - -
R3‑002241 - - -
R3‑002242 - - -
R3‑002243 - - -
R3‑002244 - - -
R3‑002245 - - -
R3‑002246 Updated Iu UP CR on selection of PDU Type 1 for NT CS data services R3 -
R3‑002247 - - -
R3‑002248 CRCI octet when number of TBs is equal to zero - -
R3‑002249 Changes to 25.435 required to support the signaling of the ‘DSCH DL signaling frame’ from the CRNC to the Node B - -
R3‑002250 - - -
R3‑002251 - - -
R3‑002252 Node B knowledge of timing advance - -
R3‑002253 - - -
R3‑002254 TDD CCTrCH power control ambiguity - -
R3‑002255 TDD CCTrCH power control ambiguity - -
R3‑002256 Edditorial Correction in Tabular format for CPCH - -
R3‑002257 Correction to RL Addition, Transmit Diversity Indicator - -
R3‑002258 Correction to RL Addition, RL Reconfiguration Prepare, and RL Configuration Request Transmit Diversity parameters - -
R3‑002259 Initial DL transmission power allocation in DRNC - -
R3‑002260 Power Offset for AP-AICH, CD/CA-ICH and CSICH - -
R3‑002261 Editorial Correction - Min SF - -
R3‑002262 - - -
R3‑002265 Usage of DRX Cycle Length Coefficient is missing - -
R3‑002266 Usage of Subflow SDU size - -
R3‑002267 - - -
R3‑002268 - - -
R3‑002269 Cause value needed for relocation - -
R3‑002270 Editorial correction of reference No - -
R3‑002271 - - -
R3‑002272 Changes to NBAP to support the signaling of the ‘DSCH DL signaling frame’ from the CRNC to the Node B - -
R3‑002273 AAL2 switching possibility - -
R3‑002274 - - -
R3‑002275 - - -
R3‑002276 - - -
R3‑002277 UL/DL SIR target corrections - -
R3‑002278 - - -
R3‑002279 - - -
R3‑002280 Remove Unnecessary use of the ProtocolIE-Container - -
R3‑002281 - - -
R3‑002282 RNSAP Support for switching from Cell_DCH to URA_PCH State - -
R3‑002283 Delay Evaluation in TR 25.932 "Delay Budget in the Access Stratum" R3 -
R3‑002284 - - -
R3‑002285 - - -
R3‑002286 Editorial Corrections in the presentation of SABP as per Specification Notation. - -
R3‑002287 - - -
R3‑002288 Node B knowledge of timing advance - -
R3‑002289 Minimum power level - -
R3‑002290 - - -
R3‑002291 - - -
r3‑002292 - - -
R3‑002293 - - -
R3‑002294 Clarification of the Resource Status Indication procedure text - -
R3‑002296 - - -
R3‑002297 - - -
R3‑002298 - - -
r3‑002300 - - -
r3‑002301 Correction to range of repetition indicator - -
r3‑002302 Correction to range of repetition indicator - -
r3‑002303 - - -
r3‑002304 Correction to range of repetition indicator - -
R3‑002305 NBAP Reset procedure - -
R3‑002306 Reply to Liaison Statement on Synchronisation Issues during Codec Type Change (R3-002013) R3 -
R3‑002307 - - -
R3‑002308 - - -
R3‑002310 - - -
R3‑002311 Rules for RANAP on how IEs become known and clarification on EP knowledge - -
R3‑002312 Rules for RNSAP on how IEs become known and clarification on EP knowledge - -
R3‑002313 Rules for NBAP on how IEs become known and clarification on EP knowledge - -
R3‑002314 Rules for SABP on how IEs become known and clarification on EP - -
R3‑002315 - - -
R3‑002316 - - -
R3‑002317 Alignment of list of functions and cleaning of editorial notes - -
R3‑002318 RAN3 REVISIONS OF THE REVISED OVERVIEWS OF IMT-2000 CDMA TDD AND FDD R3 -
R3‑002319 Procedure text proposal for optional IE in common transport channels - -
R3‑002320 Non-core Features in NBAP - -
R3‑002321 - - -
R3‑002322 - - -
R3‑002323 New Abstract syntax error for wrong order or number or IEs - -
R3‑002324 New Abstract syntax error for wrong order or number or IEs - -
R3‑002325 New Abstract syntax error for wrong order or number or IEs - -
R3‑002326 - - -
R3‑002327 - - -
R3‑002334 Physical Shared Channel procedure clarifications - -
R3‑002335 - - -
R3‑002336 Correction to Compressed Mode - -
R3‑002337 Handling of the situation when Relocation is not supported by target. - -
R3‑002338 Subflow SDUs in Payload fields - -
R3‑002339 Clarification of Message Identifier - -
R3‑002340 Support for CELL_FACH to CELL_DCH state transition - -
R3‑002341 Correcting the references in SABP & other minor corrections. - -
R3‑002342 Clarification of the description and usage of Elementary Procedures. - -
R3‑002343 Proposed liaison on: FDD RACH/PRACH modelling R3 -
R3‑002344 - - -
R3‑002345 Pilot bit sending when unknown TFCI - -
R3‑002346 Procedure Rejection in RNSAP due to Lack of Support on NBAP - -
R3‑002347 Non-core Features in RNSAP - -
R3‑002348 - - -
R3‑002349 - - -
R3‑002350 - - -
R3‑002351 - - -
R3‑002352 Response to LS on RAB ASSIGNMENT FOR TRFO R3 -
R3‑002353 Answer on Directed Retry in UMTS and Inter-System R3 -
R3‑002354 - - -
R3‑002355 - - -
R3‑002356 - - -
r3‑002357 - - -
R3‑002358 - - -
R3‑002359 Response to the LS on Transition from CELL_DCH to CELL_PCH and URA_PCH states R3 -
R3‑002360 RESPONSE TO LIAISON STATEMENT ON “TWO PHASE RESOURCE RESERVATION” R3 -
R3‑002361 Procedure Rejection in RNSAP due to Unknown Procedure ID - -
R3‑002362 Update of RL-SETUP procedure text, addressing optional IE’s. - -
R3‑002363 RL addition procedure text update. - -
R3‑002364 Timeslot ISCP for TDD Node B downlink power control R3 -
R3‑002365 Editorial modification of 25.427 - -
R3‑002366 procedure rejection in NBAP due to unknown procedure ID - -
R3‑002367 RESPONSE TO LIAISON STATEMENT ON “TFCI IN THE CASE OF INVALID SET OF TRANSPORT BLOCKS AND DURING DPCH SYNCHRONISATION” R3 -
R3‑002368 Response to LS on TDD Node B synchronisation R3 -
r3‑002370 Correction to range of repetition indicator - -
r3‑002371 - - -
R3‑002372 Combined ASN.1 definition based on agreed CRs. - -
R3‑002373 Layered architecture view - -
R3‑002374 NBAP FDD IE's extension capability - -
R3‑002375 New Abstract syntax error for wrong order or number or IEs - -
R3‑002376 Combined ASN.1 definition based on agreed CRs. - -
R3‑002377 Extensability RNSAP FDD IEs - -
R3‑002378 RNSAP TDD IEs - -
R3‑002379 RNSAP Common IEs - -
R3‑002380 Extensibility for NBAP-TDD-Ies - -
r3‑002381 Updated NBAP Sync RL Reconfiguration Procedure (Optional IEs - -
r3‑002382 Updated NBAP UnSync RL Reconfiguration Procedure (Optional IEs) - -

page generated from database: 2024-03-25 09:25:51

Get news. Get knowledge. Get involved
Get news.
Get knowledge.
Get involved.
Image
The 5G Standard
3GPP General Enquiries:
info@3gpp.org 


Connect:

Quick Links