Tech-invite3GPPspecsGlossariesIETFRFCsGroupsSIPABNFsWorld Map
Top   in Index   Prev   Next

TS 25.301 (RAN6)
UTRA – Radio interface protocol architecture

ToC   3GPP‑Page   ETSI‑search   Help    
V14.0.0 (PDF)  2017/03  55 p.
V13.0.0  2016/01  55 p.
V12.0.0  2014/09  55 p.
V11.0.0  2012/09  55 p.
V10.0.0  2011/03  55 p.
V9.2.0  2010/06  55 p.
V8.7.0  2010/06  55 p.
V7.5.0  2010/06  51 p.
V6.6.0  2008/03  50 p.
V5.6.0  2005/10  45 p.
V4.4.0  2002/09  41 p.
V3.11.0  2002/09  41 p.


Rapporteur:  Mr. Van Der Zee, Martin
See also:  –

This TS shall provide an overview and overall description of the UE-UTRAN radio interface protocol architecture as agreed within the TSG RAN working group 2. Details of the radio protocols will be specified in companion documents.


 

Here   Top

 

 

1  Scope [R3]PDF-p. 6
2  References [R3]
3  Definitions and abbreviations [R3]PDF-p. 7
4  Assumed UMTS Architecture [R3]PDF-p. 8
5  Radio interface protocol architecture [R3]PDF-p. 9
5.1  Overall protocol structure
5.2  Layer 1 Services and FunctionsPDF-p. 12
5.3  Layer 2 Services and Functions
5.3.1  MAC Services and Functions
5.3.2  RLC Services and FunctionsPDF-p. 20
5.3.3  PDCP Services and Function
5.3.4  Broadcast/Multicast Control - Services and functionsPDF-p. 22
5.3.5  Data flows through Layer 2Up
5.3.5.1  Data flow for BCCH mapped to BCHPDF-p. 27
5.3.5.2  Data flow for BCCH mapped to FACHPDF-p. 28
5.3.5.3  Data flow for PCCH mapped to PCH
5.3.5.4  Data flow for CCCH mapped to FACH/RACH
5.3.5.5  Data flow for SHCCH mapped to USCH
5.3.5.6  Data flow for SHCCH mapped to FACH/RACH
5.3.5.7  Data flow for DCCH mapped to FACH/RACH
5.3.5.8  Data flow for DCCH mapped to DSCH
5.3.5.9  Data flow for DCCH mapped to USCH
5.3.5.10Void
5.3.5.11  Data flow for DTCH (non-transparent RLC) mapped to FACH/RACHUp
5.3.5.12  Data flow for DTCH (non-transparent RLC) mapped to DSCHPDF-p. 29
5.3.5.13  Data flow for DTCH (non-transparent RLC) mapped to USCH
5.3.5.14  Data flow for DTCH (transparent RLC) mapped to DCH
5.3.5.15  Data flow for DTCH (non-transparent RLC) mapped to DCH
5.3.5.16Void
5.3.5.17  Data flow for DCCH mapped to DCH
5.3.5.18  Data flow for CTCH mapped to FACH
5.3.5.19  Data flow for DCCH mapped to HS-DSCH [R5]
5.3.5.20  Data flow for DTCH (non-transparent RLC) mapped to HS-DSCH [R5]
5.3.5.21  Data flow for DCCH mapped to E-DCH [R6]
5.3.5.22  Data flow for DTCH (non-transparent RLC) mapped to E-DCH [R6]PDF-p. 30Up
5.3.5.23  Data flow for MCCH (non-transparent RLC) mapped to FACH [R6]
5.3.5.24  Data flow for MSCH (non-transparent RLC) mapped to FACH [R6]
5.3.5.25  Data flow for MTCH (non-transparent RLC) mapped to FACH [R6]
5.3.5.26  Data flow for CCCH mapped to HS-DSCH/RACH (FDD only) [R7]
5.3.5.27  Data flow for PCCH mapped to HS-DSCH [R7]
5.3.5.28  Data flow for BCCH mapped to HS-DSCH (FDD and 1.28 Mcps TDD only) [R7]
5.3.5.29  Data flow for CCCH mapped to HS-DSCH/E-DCH (FDD and 1.28 Mcps TDD only) [R8]
5.3.6  Transport Channel, Logical Channel and MAC-d flow Numbering
5.4  Layer 3 - Uu Stratum Services and FunctionsPDF-p. 32
5.5  Interactions between RRC and lower layers in the C planePDF-p. 35
5.6  Protocol terminationPDF-p. 36
6  User Identification and RRC Connection Mobility [R3]PDF-p. 49
7  UE modes [R3]PDF-p. 51
A  Change historyPDF-p. 52

Up   Top