TS 25.301 V3.2.0 (1999-10)
`
`Technical Specification
`
`3rd Generation Partnership Project (3GPP);
`Technical Specification Group (TSG) RAN;
`Working Group 2 (WG2);
`
`Radio Interface Protocol Architecture
`
`
`
`
`
`The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of
`3GPP.
`
`The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
`This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this
`Specification.
`Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' Publications Offices.
`
`
`
`
`
`Page 1 of 51
`
`

`

`Reference
`<Workitem> (<Shortfilename>.PDF)
`
`Keywords
`Digital cellular telecommunications system,
`Universal Mobile Telecommunication System
`(UMTS), UTRA, IMT-2000
`
`3GPP
`
`Postal address
`
`Office address
`
`Internet
`secretariat@3gpp.org
`Individual copies of this deliverable
`can be downloaded from
`http://www.3gpp.org
`
`Copyright Notification
`
`No part may be reproduced except as authorized by written permission.
`The copyright and the foregoing restriction extend to reproduction in all media.
`
`© 1999, 3GPP Organizational Partners (ARIB, CWTS, ETSI, T1, TTA,TTC).
`All rights reserved.
`
`Page 2 of 51
`
`

`

`Contents
`
`Contents .............................................................................................................................................................. 3
`
`Foreword ............................................................................................................................................................ 5
`
`1
`
`2
`
`3
`3.1
`3.2
`
`Scope ........................................................................................................................................................ 6
`
`References ................................................................................................................................................ 6
`
`Definitions and Abbreviations ................................................................................................................. 7
`Definitions ......................................................................................................................................................... 7
`Abbreviations ..................................................................................................................................................... 7
`
`4
`
`Assumed UMTS Architecture ................................................................................................................ 10
`
`5
`5.1
`5.1.1
`5.2
`5.2.1
`5.2.1.1
`5.2.2
`5.3
`5.3.1
`5.3.1.1
`5.3.1.1.1
`5.3.1.1.1.1
`5.3.1.1.1.2
`5.3.1.1.2
`5.3.1.2
`5.3.2
`5.3.2.1
`5.3.2.2
`5.3.3
`5.3.3.1
`5.3.3.2
`5.3.4
`5.3.4.1
`5.3.4.2
`5.3.5
`5.3.5.1
`5.3.5.2
`5.3.5.3
`5.3.5.4
`5.3.5.5
`5.3.5.6
`5.3.5.7
`5.3.5.8
`5.3.5.9
`5.3.5.10
`5.3.5.11
`5.3.5.12
`5.3.5.13
`5.3.5.14
`5.3.5.15
`5.3.5.16
`5.3.5.17
`5.3.5.18
`5.4
`
`Radio interface protocol architecture ..................................................................................................... 12
`Overall protocol structure ................................................................................................................................ 12
`Service access points and service primitives .............................................................................................. 14
`Layer 1 Services and Functions ....................................................................................................................... 14
`L1 Services ................................................................................................................................................. 15
`Transport channels ................................................................................................................................ 15
`L1 Functions ............................................................................................................................................... 16
`Layer 2 Services and Functions ...................................................................................................................... 16
`MAC Services and Functions ..................................................................................................................... 16
`MAC Services to upper layers .............................................................................................................. 16
`Logical channels ............................................................................................................................. 17
`Control Channels ....................................................................................................................... 17
`Traffic Channels ........................................................................................................................ 18
`Mapping between logical channels and transport channels ............................................................. 18
`MAC functions ..................................................................................................................................... 20
`RLC Services and Functions ...................................................................................................................... 21
`Services provided to the upper layer..................................................................................................... 21
`RLC Functions ...................................................................................................................................... 22
`PDCP Services and Function ..................................................................................................................... 23
`PDCP Services provided to upper layers .............................................................................................. 23
` PDCP Functions ................................................................................................................................. 23
`Broadcast/Multicast Control – Services and functions ............................................................................... 23
`BMC Services ....................................................................................................................................... 23
`BMC Functions..................................................................................................................................... 23
`Data flows through Layer 2 ........................................................................................................................ 23
`Data flow for BCCH mapped to BCH .................................................................................................. 26
`Data flow for BCCH mapped to FACH ................................................................................................ 26
`Data flow for PCCH mapped to PCH ................................................................................................... 26
`Data flow for SCCH mapped to SCH (ffs.) .......................................................................................... 26
`Data flow for CCCH mapped to FACH/RACH (ffs) ............................................................................ 26
`Data flow for SHCCH mapped to FACH/RACH ................................................................................. 26
`Data flow for DCCH mapped to FACH/RACH .................................................................................... 27
`Data flow for DCCH mapped to DSCH................................................................................................ 27
`Data flow for DCCH mapped to USCH................................................................................................ 27
`Data flow for DCCH mapped to CPCH ................................................................................................ 27
`Data flow for DTCH (non-transparent RLC) mapped to FACH/RACH ............................................... 27
`Data flow for DTCH (non-transparent RLC) mapped to DSCH ........................................................... 27
`Data flow for DTCH (non-transparent RLC) mapped to USCH ........................................................... 27
`Data flow for DTCH (transparent RLC) mapped to DCH .................................................................... 27
`Data flow for DTCH (non-transparent RLC) mapped to DCH ............................................................. 27
`Data flow for DTCH (non-transparent RLC) mapped to CPCH. .......................................................... 27
`Data flow for DCCH mapped to DCH .................................................................................................. 28
`Data flow for CTCH mapped to FACH ................................................................................................ 28
`Layer 3 – Uu Stratum Services and Functions ................................................................................................. 28
`
`Page 3 of 51
`
`

`

`5.4.1
`5.4.1.1
`5.4.1.2
`5.4.1.3
`5.4.2
`5.5
`5.6
`5.6.1
`5.6.2
`5.6.3
`5.6.4
`5.6.5
`5.6.5.1
`5.6.5.2
`5.6.5.2.1
`5.6.5.2.2
`5.6.5.2.3
`5.6.5.3
`5.6.5.4
`5.6.6
`5.6.6.1
`5.6.6.2
`5.6.6.3
`5.6.6.4
`5.6.7
`5.6.8
`5.6.9
`5.6.10
`5.6.11
`
`Uu Stratum services.................................................................................................................................... 28
`General Control .................................................................................................................................... 28
`Notification ........................................................................................................................................... 28
`Dedicated Control ................................................................................................................................. 29
`RRC functions ............................................................................................................................................ 29
`Interactions between RRC and lower layers in the C plane ............................................................................. 31
`Protocol termination ........................................................................................................................................ 32
`Protocol termination for DCH .................................................................................................................... 32
`Protocol termination for RACH/FACH ...................................................................................................... 32
`Protocol termination for FAUSCH ............................................................................................................. 34
`Protocol termination for CPCH .................................................................................................................. 34
`Protocol termination for DSCH .................................................................................................................. 34
`DSCH definition ................................................................................................................................... 34
`Resource allocation and UE identification on DSCH ........................................................................... 35
`Case A (UE requires a downlink TFCI on a DPCCH) ................................................................... 35
`Case B (UE requires a downlink DSCH Control Channel) ............................................................. 35
`Case C (UE requires a downlink SHCCH) (TDD only) .................................................................. 36
`Model of DSCH in UTRAN ................................................................................................................ 36
`Protocol termination ............................................................................................................................. 37
`Protocol termination for transport channel of type USCH ......................................................................... 37
`USCH definition ................................................................................................................................... 37
`Resource allocation and UE identification on USCH ........................................................................... 38
`Model of USCH in UTRAN ................................................................................................................ 38
`Protocol termination ............................................................................................................................. 38
`Protocol termination for transport channel of type BCH ............................................................................ 39
`Protocol termination for transport channel of type PCH ............................................................................ 40
`Protocol termination for transport channel of type SCH ............................................................................ 40
`Protocol termination for ODCH ................................................................................................................. 40
`Protocol termination for ORACH .............................................................................................................. 41
`
`6
`6.1
`6.2
`
`User Identification and RRC Connection Mobility ............................................................................... 42
`UE identification on the radio interface ........................................................................................................... 42
`UE connection to UTRAN ............................................................................................................................... 43
`
`7
`
`UE modes ............................................................................................................................................... 43
`
`8
`8.1
`8.2
`8.2.1
`8.2.2
`8.2.2.1
`8.2.2.2
`8.2.2.3
`8.2.2.4
`8.2.2.5
`
`Ciphering ................................................................................................................................................ 44
`Location of ciphering function in the UTRAN protocol architecture .............................................................. 44
`Input parameters to the ciphering algorithm .................................................................................................... 44
`Overview .................................................................................................................................................... 44
`Ciphering algorithms parameters ................................................................................................................ 44
`COUNT ................................................................................................................................................ 44
`Ciphering key, CK ................................................................................................................................ 45
`BEARER .............................................................................................................................................. 45
`Direction ............................................................................................................................................... 46
`Length ................................................................................................................................................... 46
`
`Annex A (informative): Protocol termination .................................................................................................. 47
`
`History .............................................................................................................................................................. 51
`
`
`
`
`
`
`
`
`Page 4 of 51
`
`

`

` Foreword
`
`This Technical Specification has been produced by the 3GPP.
`
`The contents of the present document are subject to continuing work within the TSG and may change following formal
`TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying
`change of release date and an increase in version number as follows:
`
`Version 3.y.z
`
`where:
`
`x
`
`the first digit:
`
`1 presented to TSG for information;
`
`2 presented to TSG for approval;
`
`3 Indicates TSG approved document under change control.
`
`y
`
`the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates,
`etc.
`
`z
`
`the third digit is incremented when editorial only changes have been incorporated in the specification.
`
`
`
`
`
`Page 5 of 51
`
`

`

`1 Scope
`
`The present document shall provide an overview and overall description of the UE-UTRAN radio interface protocol
`architecture as agreed within the 3GPP TSG RAN working group 2. Details of the radio protocols will be specified in
`companion documents.
`
`2 References
`
`The following documents contain provisions which, through reference in this text, constitute provisions of the present
`document.
`
`· References are either specific (identified by date of publication, edition number, version number, etc.) or
`non-specific.
`
`· For a specific reference, subsequent revisions do not apply.
`
`· For a non-specific reference, the latest version applies.
`
`· A non-specific reference to a TS shall also be taken to refer to later versions published as an EN with the same
`number.
`
`[1] 3GPP TS 23.110: “UMTS Access Stratum; Services and Functions”
`
`[2] 3GPP TS 25.401: “RAN Overall Description”
`
`[3] 3GPP TR 25.945: “Vocabulary for the UTRAN”
`
`[4] 3GPP TS 25.302: “Services Provided by the Physical Layer”
`
`[5] 3GPP TS 25.303: “UE Functions and Inter-Layer Procedures in Connected Mode”
`
`[6] 3GPP TS 25.304: “UE Procedures in Idle Mode”
`
`[7] 3GPP TS 25.321: “MAC Protocol Specification”
`
`[8] 3GPP TS 25.322: “RLC Protocol Specification”
`
`[9] 3GPP TS.25.331: “RRC Protocol Specification”
`
`[10] 3GPP TS 25.224: “Physical Layer Procedures (TDD)”
`
`Page 6 of 51
`
`

`

`3 Definitions and Abbreviations
`
`3.1 Definitions
`
`See [3] for a definition of fundamental concepts and vocabulary.
`
`3.2 Abbreviations
`
`
`
`ARQ
`
`ASC
`
`
`
`BCCH
`
`BCH
`
`
`
`BMC
`
`C-
`
`CC
`
`
`
`CCCH
`
`CCH
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` Automatic Repeat Request
`
` Access Service Class
`
` Broadcast Control Channel
`
` Broadcast Channel
`
` Broadcast/Multicast Control
`
`Control-
`
` Call Control
`
` Common Control Channel
`
` Control Channel
`
`CCTrCH
`
` Coded Composite Transport Channel
`
`CN
`
`
`
`CPCH
`
`CRC
`
`
`
`CTCH
`
`DC
`
`
`
`DCA
`
`DCCH
`
`DCH
`
`DL
`
`
`
`DRNC
`
`DSCH
`
`DTCH
`
`FACH
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`FAUSCH
`
`FCS
`
`FDD
`
`GC
`
`
`
`
`
`
`
`
`
`
`
`
`
` Core Network
`
` Common Packet channel
`
` Cyclic Redundancy Check
`
` Common Traffic Channel
`
` Dedicated Control (SAP)
`
` Dynamic Channel Allocation
`
` Dedicated Control Channel
`
` Dedicated Channel
`
` Downlink
`
` Drift Radio Network Controller
`
` Downlink Shared Channel
`
` Dedicated Traffic Channel
`
`
`
`
`
`
`
`
`
`Forward Link Access Channel
`
`Fast Uplink Signalling Channel
`
`Frame Check Sequence
`
`Frequency Division Duplex
`
` General Control (SAP)
`
`Page 7 of 51
`
`

`

`HO
`
`ITU
`
`kbps
`
`L1
`
`L2
`
`L3
`
`LAC
`
`LAI
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`MAC
`
`MM
`
`Nt
`
`
`
`
`
`OCCCH
`
`ODCCH
`
`ODCH
`
`ODMA
`
`ORACH
`
`ODTCH
`
`PCCH
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` Handover
`
`
`
`
`
`International Telecommunication Union
`
`kilo-bits per second
`
` Layer 1 (physical layer)
`
` Layer 2 (data link layer)
`
` Layer 3 (network layer)
`
` Link Access Control
`
` Location Area Identity
`
` Medium Access Control
`
` Mobility Management
`
` Notification (SAP)
`
` ODMA Common Control Channel
`
` ODMA Dedicated Control Channel
`
` ODMA Dedicated Channel
`
` Opportunity Driven Multiple Access
`
` ODMA Random Access Channel
`
` ODMA Dedicated Traffic Channel
`
`
`
`Paging Control Channel
`
`PCH
`
`PDCP
`
`PDU
`
`PU
`
`PHY
`
`
`
`
`
`
`
`PhyCH
`
`RAB
`
`
`
`RACH
`
`RLC
`
`RNC
`
`RNS
`
`
`
`
`
`
`
`RNTI
`
`RRC
`
`SAP
`
`
`
`
`
`SCCH
`
`SCH
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Paging Channel
`
`Packet Data Convergence Protocol
`
`Protocol Data Unit
`
`Payload Unit
`
`Physical layer
`
`Physical Channels
`
` Radio Access Bearer
`
` Random Access Channel
`
` Radio Link Control
`
` Radio Network Controller
`
` Radio Network Subsystem
`
` Radio Network Temporary Identity
`
` Radio Resource Control
`
`
`
`
`
`
`
`Service Access Point
`
`Synchronization Control Channel
`
`Synchronization Channel
`
`Page 8 of 51
`
`

`

`SDU
`
`
`
`SHCCH
`
`SRNC
`
`SRNS
`
`TCH
`
`TDD
`
`
`
`
`
`TFCI
`
`TFI
`
`
`
`TMSI
`
`TPC
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Service Data Unit
`
`Shared Channel Control Channel
`
`Serving Radio Network Controller
`
`Serving Radio Network Subsystem
`
` Traffic Channel
`
` Time Division Duplex
`
` Transport Format Combination Indicator
`
` Transport Format Indicator
`
` Temporary Mobile Subscriber Identity
`
` Transmit Power Control
`
`U- User-
`
` User Equipment
`
` User Equipment with ODMA relay operation enabled
`
` Uplink
`
` Universal Mobile Telecommunications System
`
` UTRAN Registration Area
`
` Uplink Shared Channel
`
` UMTS Terrestrial Radio Access
`
` UMTS Terrestrial Radio Access Network
`
`UE
`
`UER
`
`UL
`
`
`
`
`
`
`
`UMTS
`
`URA
`
`USCH
`
`UTRA
`
`UTRAN
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Page 9 of 51
`
`

`

`4 Assumed UMTS Architecture
`
`Figure 1 shows the assumed UMTS architecture as outlined in TS 23.110 [1]. The figure shows the UMTS architecture
`in terms of its entities User Equipment (UE), UTRAN and Core Network. The respective reference points Uu (Radio
`Interface) and Iu (CN-UTRAN interface) are shown. The figure illustrates furthermore the high-level functional
`grouping into the Access Stratum and the Non-Access Stratum.
`
`The Access Stratum offers services through the following Service Access Points (SAP) to the Non-Access Stratum:
`
` General Control (GC) SAPs,
`
` Notification (Nt) SAPs and
`
` Dedicated Control (DC) SAPs
`
`The SAPs are marked with circles in Figure 1.
`
`Figure 1: Assumed UMTS Architecture
`
`
`
`
`This model can be further refined to distinguish the end AS entities, which provide the services to higher layers, from
`the local entities, which provide services over respectively the Uu and the Iu reference point. Figure 1b presents the
`refined model.
`
`Non-Access Stratum
`
`GC
`
`Nt
`
`DC
`
`GC
`
`Nt
`
`DC
`
`Access Stratum
`
`UE
`
`UTRAN
`
`Core Network
`
`Radio
`(Uu)
`
`Iu
`
`Page 10 of 51
`
`

`

`Figure 1b: Assumed UTRAN Model
`The Uu Stratum block can be further refined as shown in Figure 1c:
`
`
`
`Figure 1c: Assumed Uu Stratum Model
`
`
`
`
`
`GC
`
`Nt
`
`DC
`
`GC
`
`Nt
`
`DC
`
`GC
`
`Nt
`
`DC
`
`GC
`
`Nt
`
`DC
`
`GC
`
`Nt
`
`DC
`
`GC
`
`Nt
`
`DC
`
`Relay
`
`Uu Stratum
`
`Iu Stratum
`
`UE
`
`Radio
`(Uu)
`
`UTRAN
`
`Core Network
`
`Iu
`
`GC
`
`Nt
`
`DC
`
`GC
`
`Nt
`
`DC
`
`RRC
`
`RRC
`
`bearers
`
`RLC/MAC/PHY
`
`RLC/MAC/PHY
`
`UE
`
`UTRAN
`
`Radio
`(Uu)
`
`Page 11 of 51
`
`

`

` 5
`
` Radio interface protocol architecture
`
`5.1 Overall protocol structure
`
`The radio interface is layered into three protocol layers:
`
`
`
`
`
`
`
`the physical layer (L1),
`
`the data link layer (L2),
`
`network layer (L3).
`
`Layer 2 is split into following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data
`Convergence Protocol (PDCP) and Broadcast/Multicast Control (BMC).
`
`Layer 3 and RLC are divided into Control (C-) and User (U-) planes. PDCP and BMC exist in the U-plane only.
`
`In the C-plane, Layer 3 is partitioned into sublayers where the lowest sublayer, denoted as Radio Resource Control
`(RRC), interfaces with layer 2 and terminates in the UTRAN. The next sublayer, denoted 'Duplication avoidance'
`[TBD], terminates in the CN but is part of the Access Stratum; it provides the Access Stratum Services to higher layers..
`The higher layer signalling such as Mobility Management (MM) and Call Control (CC) are assumed to belong to the
`non-access stratum, and therefore not in the scope of 3GPP TSG RAN. On the general level, the protocol architecture is
`similar to the current ITU-R protocol architecture, ITU-R M.1035.
`
`Figure 2 shows the radio interface protocol architecture. Each block in Figure 2 represents an instance of the respective
`protocol. Service Access Points (SAP) for peer-to-peer communication are marked with circles at the interface between
`sublayers. The SAP between MAC and the physical layer provides the transport channels (cf. Sec. 5.2.1.1). The SAPs
`between RLC and the MAC sublayer provide the logical channels (cf. Sec. 5.3.1.1.1). In the C-plane, the interface
`between 'Duplication avoidance' and higher L3 sublayers (CC, MM) is defined by the General Control (GC),
`Notification (Nt) and Dedicated Control (DC) SAPs.
`
`Also shown in the figure are connections between RRC and MAC as well as RRC and L1 providing local inter-layer
`control services. An equivalent control interface exists between RRC and the RLC sublayer, between RRC and the
`PDCP sublayer and between RRC and BMC sublayer. These interfaces allow the RRC to control the configuration of
`the lower layers. For this purpose separate Control SAPs are defined between RRC and each lower layer (PDCP, RLC,
`MAC, and L1). It is assumed that for RLC and MAC one Control SAP each is provided per UE.
`
`[Note: Control of RLC entities in C and U planes needs to be clarified further. Also, the multiplicity of Control SAPs
`(necessity of one SAP per UE) at the UTRAN side may need to be reconsidered.]
`
`The RLC sublayer provides ARQ functionality closely coupled with the radio transmission technique used. There is no
`difference between RLC instances in C and U planes.
`
`The UTRAN can be requested by the CN to prevent all loss of data (i.e. independently of the handovers on the radio
`interface), as long as the Iu connection point is not modified. This is a basic requirement to be fulfilled by the UTRAN
`retransmission functionality as provided by the RLC sublayer.
`
`However, in case of the Iu connection point is changed (e.g. SRNS relocation, streamlining), the prevention of the loss
`of data may not be guaranteed autonomously by the UTRAN but relies on some functions in the 'Duplication avoidance'
`layer. Such mechanisms to protect from data loss due to SRNS relocation or streamlining are for further study.
`
`[Note: Such mechanisms need to be specified jointly with 3GPP TSGs CN and SA. The implied functionality would be
`applied in the U plane. Applicability in the C plane is for further study.]
`
`
`
`Page 12 of 51
`
`

`

`Figure 2: Radio Interface protocol architecture (Service Access Points marked by circles)
`
`
`
`C-plane signalling
`
`U-plane information
`
`GC
`
`Nt
`
`DC
`
`Duplication avoidance
`
`GC
`
`Nt
`
`DC
`
`L3
`
`control
`
`RRC
`
`UuS boundary
`
`PDCP
`
`PDCP
`
`L2/PDCP
`
`BMC
`
`L2/BMC
`
`control
`
`control
`
`control
`
`control
`
`RLC
`
`RLC
`
`RLC
`
`RLC
`
`RLC
`
`RLC
`
`RLC
`
`RLC
`
`L2/RLC
`
` MAC
`
`PHY
`
`Logical
`Channels
`
`L2/MAC
`
`Transport
`Channels
`
`L1
`
`Page 13 of 51
`
`

`

`5.1.1
`
`Service access points and service primitives
`
`Each layer provides services at Service Access Points (SAPs). A service is defined by a set of service primitives
`(operations) that a layer provides to upper layer(s).
`
`Control services, allowing the RRC layer to control lower layers locally (i.e. not requiring peer-to-peer communication)
`are provided at Control SAPs (C-SAP). Note that C-SAP primitives can bypass one or more sublayers, see Figure 2.
`
`In the radio interface protocol specifications, the following naming conventions for primitives shall be applicable:
`
` Primitives provided by SAPs between adjacent layers shall be prefixed with the name of the service-providing
`layer, i.e. PHY, MAC, RLC, PDCP orUUS.
`
` Primitives provided by SAPs to an application shall be prefixed with the name of the service-providing layer, i.e.
`RRC.
`
` Primitives provided by Control SAPs, in addition to the name of the service-providing layer, shall be prefixed with
`a “C”, i.e. CPHY, CMAC, CRLC or CPDCP.
`
`This principle leads to the following notations, where <Type> corresponds to request, indication, response or confirm
`type of primitives:
`
`
`
`
`
`Primitives between PHY and MAC:
`PHY- <Generic name> – <Type>
`
`Primitives between PHY and RRC (over C-SAP):
`CPHY- <Generic name> - <Type>
`
`Primitives between MAC and RLC:
`MAC- <Generic name> - <Type>
`
`Primitives between MAC and RRC (over C-SAP):
`CMAC- <Generic name> - <Type>
`
`Primitives between RLC and upper layers, between RLC and RRC for data transfer and between RLC and PDCP:
`RLC- <Generic name> - <Type>
`
`Primitives between RLC and RRC for control of RLC (over C-SAP):
`CRLC- <Generic name> – <Type>
`
`Primitives above Uu Stratum:
`UUS- <Generic name> – <Type>
`
`Primitives between PDCP and non-access stratum:
`PDCP- <Generic name> - <Type>
`
`Primitives between PDCP and RRC (over C-SAP):
`CPDCP- <Generic name> - <Type>
`
`Primitives between BMC and RRC for control of BMC (over C-SAP):
`CBMC- <Generic name> – <Type>
`
`In this model, some UUS primitives map directly to RLC primitives without intervening function.
`
`5.2 Layer 1 Services and Functions
`
`This section shall provide an overview on services and functions provided by the physical layer. A detailed description
`of Layer 1 general requirements can be found in 3GPP TS 25.302 [4].
`
`Page 14 of 51
`
`

`

`5.2.1
`
` L1 Services
`
`The physical layer offers information transfer services to MAC and higher layers. The physical layer transport services
`are described by how and with what characteristics data are transferred over the radio interface. An adequate term for
`this is ‘Transport Channel’1.
`
`5.2.1.1
`
`Transport channels
`
`A general classification of transport channels is into two groups:
`
` common transport channels (where there is a need for inband identification of the UEs when particular UEs are
`addressed) and
`
` dedicated transport channels (where the UEs are identified by the physical channel, i.e. code and frequency for FDD
`and code, time slot and frequency for TDD).
`
`Common transport channel types are (a more detailed description can be found in [4]):
`
` Random Access Channel (RACH)
`A contention based uplink channel used for transmission of relatively small amount of data, e.g. for initial access or
`non-realtime dedicated control or traffic data.
`
` ODMA Random Access Channel (ORACH)
`A contention based channel used in relaylink.
`
` Common Packet channel (CPCH)
`
`A contention based channel used for transmission of bursty data traffic. This channel only exists in FDD mode and
`only in the uplink direction. The common packet channel is shared by the UEs in a cell and therefore, it is a common
`resource. The CPCH is fast power controlled.
`
` Forward Access Channel (FACH)
`Common downlink channel without closed-loop power control used for transmission of relatively small amount of
`data.
`
` Downlink Shared Channel (DSCH)
` A downlink channel shared by several UEs carrying dedicated control or traffic data.
`
` DSCH Control Channel
` A downlink channel associated with a DSCH used for signalling of DSCH resource allocation.
`
`[Note: It is for further study whether or not the DSCH Control Channel needs to be regarded as separate transport
`channel type from FACH. Seen from the upper layers, the current requirements are identical to a FACH, but some
`extra L1 information (e.g.TPC bits) may lead to a different physical channel. See Sec. 5.6.5 for a description of the
`DSCH concepts currently considered in TSG-RAN WG2. This section also includes further notes on ffs. items
`related to the DSCH.]
`
` Uplink Shared Channel (USCH)
`An uplink channel shared by several UEs carrying dedicated control or traffic data, used in TDD mode only.
`
` Broadcast Channel (BCH)
`A downlink channel used for broadcast of system information into an entire cell.
`
` Synchronization Channel (SCH)
`A downlink channel used for broadcast of synchronization information into an entire cell in TDD mode.
`
`Note that the SCH transport channel is defined for the TDD mode only. In the FDD mode, a synchronization channel
`is defined as a physical channel. This channel however should not be confused with the SCH transport channel
`defined above.
`
` Paging Channel (PCH)
`A downlink channel used for broadcast of control information into an entire cell allow