3GPP TR 25.813 V0.6.0 (2006-03)
`
`Technical Report
`
`3rd Generation Partnership Project;
`Technical Specification Group Radio Access Network;
`Evolved Universal Terrestrial Radio Access (E-UTRA)
`and Evolved Universal Terrestrial Radio Access Network
`(E-UTRAN);
`Radio interface protocol aspects
`(Release 7)
`
`
`
`
`
`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 Organizational Partners and shall not be implemented.
`
`This Specification is provided for future development work within 3GPP only. The Organizational 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 Organizational Partners' Publications Offices.
`
`Ericsson v. IV II LLC
`Ex. 1018 / Page 1 of 26
`
`

`

`
`Release 7
`
`2
`
`3GPP TR 25.813 V0.6.0 (2006-03)
`
`.
`
`
`
`
`
`
`
`
`
`
`
`Keywords
`Evolved UTRA and UTRAN
`
`3GPP
`
`Postal address
`
`
`3GPP support office address
`650 Route des Lucioles - Sophia Antipolis
`Valbonne - FRANCE
`Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
`
`Internet
`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.
`
`© 2004, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
`All rights reserved.
`
`
`3GPP
`
`Ex. 1018 / Page 2 of 26
`
`

`

`
`Release 7
`
`3
`
`3GPP TR 25.813 V0.6.0 (2006-03)
`
`Contents
`
`Foreword ............................................................................................................................................................ 5
`Introduction ........................................................................................................................................................ 5
`1
`Scope ........................................................................................................................................................ 6
`2
`References ................................................................................................................................................ 6
`3
`Definitions, symbols and abbreviations ................................................................................................... 6
`3.1
`Definitions ............................................................................................................................................................. 6
`3.2
`Symbols ................................................................................................................................................................. 6
`3.3
`Abbreviations ........................................................................................................................................................ 6
`4
`Objectives and requirements .................................................................................................................... 7
`4.1
`Complexity ............................................................................................................................................................ 7
`4.2
`Performance .......................................................................................................................................................... 8
`5
`Protocol architecture ................................................................................................................................ 8
`5.1
`Overall protocol architecture ................................................................................................................................ 8
`5.1.1
`User plane ...................................................................................................................................................... 10
`5.1.2
`Control plane ................................................................................................................................................. 10
`5.2
`Layer 1 ................................................................................................................................................................. 10
`5.2.1
`Services and functions ................................................................................................................................... 11
`5.2.2
`Transport channels ........................................................................................................................................ 11
`5.3
`Layer 2 ................................................................................................................................................................. 12
`5.3.1
`MAC .............................................................................................................................................................. 12
`5.3.1.1
`Logical Channels ..................................................................................................................................... 13
`5.3.1.1.1
`Control Channels ............................................................................................................................... 13
`5.3.1.1.2
`Traffic Channels ................................................................................................................................ 14
`5.3.1.2
`Mapping between logical channels and transport channels .................................................................... 14
`5.3.1.2.1
`Mapping in Uplink ............................................................................................................................. 14
`5.3.1.2.2
`Mapping in Downlink ........................................................................................................................ 14
`5.3.1.3
`Services and Functions ............................................................................................................................ 15
`5.3.2
`PDCP ............................................................................................................................................................. 15
`5.3.3
`Data flows through Layer 2........................................................................................................................... 15
`5.4
`Layer 3 - RRC ..................................................................................................................................................... 16
`5.4.1
`LTE RRC protocol states & state transitions ................................................................................................ 16
`5.4.2
`Functions ....................................................................................................................................................... 17
`5.5
`Protocol termination ............................................................................................................................................ 18
`6
`ARQ and HARQ .................................................................................................................................... 18
`7
`Scheduling .............................................................................................................................................. 18
`8
`QoS Control ........................................................................................................................................... 18
`9
`Mobility .................................................................................................................................................. 18
`9.1
`Intra E-UTRAN ................................................................................................................................................... 19
`9.1.1
`UE identification on the radio interface ........................................................................................................ 19
`9.1.2
`Cell selection ................................................................................................................................................. 19
`9.1.3
`Cell reselection .............................................................................................................................................. 19
`9.1.4
`Paging ............................................................................................................................................................ 19
`9.1.5
`Handover ....................................................................................................................................................... 19
`9.1.6
`Measurements ................................................................................................................................................ 19
`9.1.6.1
`Intra-frequency ........................................................................................................................................ 19
`9.1.6.2
`Inter-frequency ........................................................................................................................................ 19
`9.1.7
`Network aspects ............................................................................................................................................ 19
`9.2
`Inter RAT ............................................................................................................................................................ 20
`9.2.1
`Cell reselection .............................................................................................................................................. 20
`9.2.2
`Handover ....................................................................................................................................................... 20
`9.2.3
`Measurements ................................................................................................................................................ 20
`
`3GPP
`
`Ex. 1018 / Page 3 of 26
`
`

`

`
`Release 7
`
`4
`
`3GPP TR 25.813 V0.6.0 (2006-03)
`
`Inter-RAT handovers from E-UTRAN ................................................................................................... 20
`9.2.3.1
`Inter-RAT Handovers to E-UTRAN ....................................................................................................... 20
`9.2.3.2
`Inter-RAT cell reselection from E-UTRAN ........................................................................................... 20
`9.2.3.3
`Limiting measurement load at UE .......................................................................................................... 20
`9.2.3.4
`Network Aspects ........................................................................................................................................... 21
`9.2.4
`Security .................................................................................................................................................. 21
`10
`Security Termination Points ............................................................................................................................... 21
`10.1
`11 MBMS .................................................................................................................................................... 21
`12 Migration and compatibility ................................................................................................................... 21
`12.1
`Migration scenario .............................................................................................................................................. 22
`12.2
`Interaction with previous releases ...................................................................................................................... 22
`12.3
`Interoperability .................................................................................................................................................... 22
`13 UE capabilities ....................................................................................................................................... 22
`14
`Impact on specifications ......................................................................................................................... 22
`14.1
`Specification methodology ................................................................................................................................. 22
`14.2
`Affected specifications ........................................................................................................................................ 22
`14.3
`New specifications .............................................................................................................................................. 22
`Annex A: Change history ............................................................................................................................... 23
`Annex B: RACH and Contention Resolution ............................................................................................... 24
`Annex C: Architecture Progress ................................................................................................................... 25
`Annex D: Editorship ....................................................................................................................................... 26
`
`
`3GPP
`
`Ex. 1018 / Page 4 of 26
`
`

`

`
`Release 7
`
`5
`
`3GPP TR 25.813 V0.6.0 (2006-03)
`
`Foreword
`This Technical Report has been produced by the 3rd Generation Partnership Project (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 the present document, it will be re-released by the TSG with an
`identifying change of release date and an increase in version number as follows:
`
`Version x.y.z
`
`where:
`
`x
`
`the first digit:
`
`1 presented to TSG for information;
`
`2 presented to TSG for approval;
`
`3 or greater 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 document.
`
`Introduction
`With enhancements such as HSDPA and Enhanced Uplink, the 3GPP radio-access technology will remain highly
`competitive for several years to come. However, to ensure competitiveness in an even longer time frame, the long-term
`evolution of the 3GPP radio-access technology is under study. Important parts of such a long-term evolution include
`reduced latency, higher user data rates, optimised support for packet services, improved system capacity and coverage,
`and reduced cost for the operator, while also reducing system complexity. In order to achieve this, evolutions of the
`radio interface as well as the radio network architecture are considered in the study item “Evolved UTRA and UTRAN”
`[1]. This document covers the Radio Interface Protocol Aspects of the study item.
`
`
`
`3GPP
`
`Ex. 1018 / Page 5 of 26
`
`

`

`
`Release 7
`
`6
`
`3GPP TR 25.813 V0.6.0 (2006-03)
`
`Scope
`1
`The purpose of this TR is to help TSG RAN WG2 to define and describe the radio interface protocol evolution under
`consideration for Evolved UTRA and UTRAN [1]. This activity involves the Radio Access Network work area of the
`3GPP studies for evolution and has impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
`This document is intended to gather the agreements rather than comparing different solutions.
`
`NOTE:
`
`this document is a living document, i.e. it is permanently updated and presented to TSG-RAN meetings.
`
`References
`2
`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. In the case of a reference to a 3GPP document (including
`a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
`Release as the present document.
`
`[1]
`
`[2]
`
`[3]
`
`[4]
`
`[5]
`
`TD RP-040461: “Proposed Study Item on Evolved UTRA and UTRAN”.
`
`3GPP TR 21.905: “Vocabulary for 3GPP Specifications”.
`
`3GPP TR 25.913: “Requirements for Evolved UTRA and UTRAN”.
`
`3GPP TR 25.912; “Feasibility Study for Evolved UTRA and UTRAN”.
`
`3GPP TR 25.814: “Physical Layer Aspects for Evolved UTRA”.
`
`3
`
`Definitions, symbols and abbreviations
`
`Definitions
`3.1
`For the purposes of the present document, the following terms and definitions apply.
`
`<defined term>: <definition>.
`
`Symbols
`3.2
`For the purposes of the present document, the following symbols apply:
`
`<Explanation>
`
`<symbol>
`
`Abbreviations
`3.3
`For the purposes of the present document, the following abbreviations apply:
`
`aGW
`ARQ
`AS
`DL
`
`E-UTRAN Access Gateway
`Automatic Repeat Request
`Access Stratum
`Downlink
`
`3GPP
`
`Ex. 1018 / Page 6 of 26
`
`

`

`
`Release 7
`
`7
`
`3GPP TR 25.813 V0.6.0 (2006-03)
`
`eNB
`E-UTRA
`E-UTRAN
`HARQ
`HO
`L1
`L2
`L3
`MAC
`NAS
`PDCP
`PDU
`RLC
`RRC
`SAE
`SDU
`TCH
`UE
`UL
`UMTS
`UTRA
`UTRAN
`
`
`
`E-UTRAN NodeB
`Evolved Universal Terrestrial Radio Access
`Evolved Universal Terrestrial Radio Access Network
`Hybrid Automatic Repeat Request
`Handover
`Layer 1 (physical layer)
`Layer 2 (data link layer)
`Layer 3 (network layer)
`Medium Access Control
`Non-Access Stratum
`Packet Data Convergence Protocol
`Protocol Data Unit
`Radio Link Control
`Radio Resource Control
`System Architecture Evolution
`Service Data Unit
`Traffic Channel
`User Equipment
`Uplink
`Universal Mobile Telecommunications System
`UMTS Terrestrial Radio Access
`UMTS Terrestrial Radio Access Network
`
`Other abbreviations used in the present document are listed in 3GPP TR 21.905 [2].
`
`Objectives and requirements
`4
`Simplification of the UTRAN protocol architecture and actual protocols is expected.
`
`Complexity
`4.1
`A key requirement of E-UTRAN is to maintain the complexity at a reasonable level. In this respect the following
`assumptions apply:
`
`- The number of transport channels will be reduced, by making use of shared channels.
`
`- Dedicated transport channels are not supported by E-UTRAN.
`
`- The number of different MAC-entities will be reduced (MAC-d not needed in the absence of dedicated transport
`channels).
`
`- Segmentation/Re-assembly function is agreed to be no longer needed on RLC.
`
`- The BMC layer and the CTCH are not needed i.e. All data broadcast will be on MBMS and on e.g. MTCH.
`
`- There is no SHO in the downlink (as currently supported for Rel-6 dedicated channels) for the shared channel, in
`case of unicast transmissions. Note: This does not preclude the potential support of other schemes such as fast
`cell selection, bi-casting, "softer HO" (L1 combining) for intra-site cases, etc.
`
`- Compressed mode should not be supported. If some transmission/reception gaps for measurement purpose have
`to be provided to the UE (exact need/case to be defined), this will be based on scheduling gaps.
`
`- Only one receiver structure will be assumed for defining the measurements and their requirements.
`
`- RRC should be simplified by e.g. reducing the number of RRC states compared to UTRAN (e.g. removal of
`CELL_FACH is agreed).
`
`3GPP
`
`Ex. 1018 / Page 7 of 26
`
`

`

`
`Release 7
`
`4.2
`Note:
`
`8
`
`3GPP TR 25.813 V0.6.0 (2006-03)
`
`Performance
`From R2-051759: U-Plane Latency < 5msec; C-Plane Latency < 100msec (from Inactive to Active);
`optimisation of User Plane for high bit rates; hide breaks from application; shorter transitions (state
`transitions, handover within UTRA?); support “always-on” efficiently.
`
`5
`
`Protocol architecture
`
`Overall protocol architecture
`5.1
`The E-UTRAN consists of eNBs, providing the E-UTRA user plane (PHY/MAC) and control plane (RRC) protocol
`terminations towards the UE. The eNBs are interconnected with each other in a meshed way and interface to the aGW
`via the S1 interface in a flexible manner.
`
`Figure 5.1 below gives an overview of the E-UTRAN architecture where:
`
`- Logical Nodes depicted as yellow-shaded boxes with solid frame are agreed.
`
`- Logical Nodes depicted as yellow-shaded boxes with dashed frame are not yet agreed.
`
`- White boxes depict the functional entities of the control plane and blue boxes depict the functional entities of the
`user plane:
`
`- Those, where an agreement on their association with logical nodes has been achieved are depicted inside this
`logical node;
`
`- Those, where an agreement on their association with logical nodes has not yet been achieved, are depicted
`outside logical nodes and their possible locations are indicated by arrows;
`
`- Those, where an agreement on their existence has been achieved are depicted with solid frames;
`
`- Those, where an agreement on their existence has not been achieved are depicted with dashed frames;
`
`
`
`3GPP
`
`Ex. 1018 / Page 8 of 26
`
`

`

`
`Release 7
`
`eNB
`
`9
`
`3GPP TR 25.813 V0.6.0 (2006-03)
`
`Inter Cell RRM
`
`Connection
`Mobility Cont.
`
`RB Control
`
`Radio
`Admission
`Control
`
`eNB
`Measurement
`Configuration &
`Provision
`
`Dynamic
`Resource
`Allocation
`(Scheduler)
`
`RRC
`
`MAC (ARQ)
`
`PHY (HARQ)
`
`RRM Server
`(optional)
`
`Inter-Cell
`RRM
`Database
`(optional)
`
`aGW Control Plane
`
`SAE Bearer
`Control
`
`MM Entity
`
`aGW User Plane
`
`PDCP
`
`Ciphering
`
`S1
`
`User Plane
`
`internet
`
`Figure 5.1: E-UTRAN Architecture
`
`
`
`The functions agreed to be hosted by the eNB are:
`
`- Selection of aGW at attachment;
`
`- Routing towards aGW at RRC activation;
`
`- Scheduling and transmission of paging messages;
`
`- Scheduling and transmission of BCCH information;
`
`- Dynamic allocation of resources to UEs in both uplink and downlink;
`
`- The configuration and provision of eNB measurements;
`
`- Radio Bearer Control;
`
`- Radio Admission Control;
`
`- Connection Mobility Control in LTE_ACTIVE mode.
`
`It remains FFS whether the aGW is split into U- and C-plane. The functions agreed to be hosted by the aGW are:
`
`- Paging origination;
`
`- LTE_IDLE mode management;
`
`- Ciphering of the user plane;
`
`- PDCP;
`
`3GPP
`
`Ex. 1018 / Page 9 of 26
`
`

`

`
`Release 7
`
`10
`
`3GPP TR 25.813 V0.6.0 (2006-03)
`
`- SAE Bearer Control.
`
`User plane
`5.1.1
`Figure 5.1.2 below shows the user-plane protocol stack for E-UTRAN, where:
`
`- A MAC-layer above the physical layer exists in both the UE and the eNB;
`
`- No separate RLC entity is introduced;
`
`- PDCP is located in the aGW on the network side but the exact functionalities that it supports need to be revisited
`compared to UTRAN.
`
`
`
`Figure 5.1.1: User-plane protocol stack
`
`
`
`Control plane
`5.1.2
`Figure 5.1.2 below shows the control-plane protocol stack for E-UTRAN. The following working assumptions apply:
`
`- Same MAC layer as in the user plane;
`
`- No separate RLC entity is introduced;
`
`- RRC terminates in the eNB on the network side.
`
`
`
`Figure 5.1.2: Control-plane protocol stack
`
`
`
`5.2
`Note:
`
`Layer 1
`This section will summarize the Layer 1 in terms of services, functions and transport channels offered to
`Layer 2 (input from WG1 and 25.814).
`
`3GPP
`
`Ex. 1018 / Page 10 of 26
`
`

`

`
`Release 7
`
`11
`
`3GPP TR 25.813 V0.6.0 (2006-03)
`
`Services and functions
`5.2.1
`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”.
`
`NOTE: This should be clearly separated from the classification of what is transported, which relates to the
`concept of logical channels at MAC layer.
`
`Transport channels
`5.2.2
`Downlink transport channel types are:
`
`1. Broadcast Channel (BCH) characterised by:
`
`-
`
`-
`
`low fixed bit rate;
`
`requirement to be broadcast in the entire coverage area of the cell.
`
`2. Downlink Shared Channel (DL-SCH) characterised by:
`
`- possibility to use HARQ;
`
`- possibility of applying link adaptation by varying the modulation, coding and transmit power;
`
`- possibility to be broadcast in the entire cell;
`
`- possibility to use beamforming;
`
`- dynamic or semi-static resource allocation;
`
`- possibility of CQI reporting;
`
`- different levels of UE activity so as to achieve UE power saving.
`
`NOTE:
`
`the possibility to use slow power control depends on the physical layer.
`
`3. Paging Channel (PCH) characterised by:
`
`-
`
`-
`
`support of UE power saving (DRX cycle is indicated by the network to the UE);
`
`requirement to be broadcast in the entire coverage area of the cell;
`
`- mapped to physical resources which can be used dynamically also for traffic/other control channels.
`
`4. Notification Channel (NCH) FFS characterised by:
`
`-
`
`-
`
`support of UE power saving;
`
`requirement to be broadcast in the entire coverage area of the cell.
`
`It is FFS whether a separate Multicast Channel (MCH) would exist or if additional attributes will be added to the
`SCH.
`
`Uplink transport channel types are:
`
`1. Uplink Shared channel (UL-SCH) characterised by:
`
`- possibility to use beamforming; (likely no impact on specifications)
`
`- possibility of applying link adaptation by varying the transmit power and potentially modulation and coding;
`
`- possibility to use HARQ;
`
`- dynamic or semi-static resource allocation; (Note: new attribute, FFS on whether there would be two types of
`UL-SCH)
`
`3GPP
`
`Ex. 1018 / Page 11 of 26
`
`

`

`
`Release 7
`
`12
`
`3GPP TR 25.813 V0.6.0 (2006-03)
`
`- possibility of CQI reporting. (Note: new attribute, FFS on whether there would be two types of UL-SCH)
`
`NOTE:
`
`the possibility to use uplink synchronisation and timing advance depend on the physical layer.
`
`It is FFS, whether a Random Access Channel is included. If yes, it would be characterised by the following
`attributes:
`
`2. Random Access Channel(s) (RACH) characterised by:
`
`-
`
`limited data field;
`
`- collision risk;
`
`- possibility to use HARQ.
`
`NOTE:
`
`the possibility to use open loop power control depends on the physical layer solution.
`
`Layer 2
`5.3
`This section gives a high level description of the Layer 2 sub-layers in terms of services and functions.
`
`5.3.1 MAC
`The MAC layer performs multiplexing of logical channels on the same HARQ process. Whether logical channels with
`the same QoS shall be multiplexed onto the same priority queue (e.g. by means of “MAC-d flows”) is FFS. If there is
`no multiplexing of logical channels onto priority queues, there is only one level of multiplexing in the MAC layer,
`similarly as in HSUPA in Release 6.
`
`NOTE: How the multiplexing relates to the QoS of the multiplexed logical channels is FFS.
`
`Figure 5.3.1a and Figure 5.3.1.b below depicts the MAC architecture for downlink and uplink respectively, where the
`multiplexing of several logical channels on the same transport channel is possible, the multiplexing of several logical
`channel on several transport channel is FFS.
`
`
`
`
`
`Figure 5.3.1a: MAC structure for DL in eNB
`
`
`
`3GPP
`
`Ex. 1018 / Page 12 of 26
`
`

`

`
`Release 7
`
`13
`
`3GPP TR 25.813 V0.6.0 (2006-03)
`
`Figure 5.3.1b: MAC structure for UL in UE
`
`
`
`
`
`Logical Channels
`5.3.1.1
`The MAC layer provides data transfer services on logical channels. A set of logical channel types is defined for
`different kinds of data transfer services as offered by MAC. Each logical channel type is defined by what type of
`information is transferred.
`
`A general classification of logical channels is into two groups:
`
`- Control Channels (for the transfer of control plane information);
`
`- Traffic Channels (for the transfer of user plane information).
`
`There is one MAC entity per cell. MAC generally consists of several function blocks (transmission scheduling
`functions, per UE functions, MBMS functions, MAC control functions, transport block generation…). Transparent
`Mode is only applied to BCCH (FFS) and PCCH.
`
`Control Channels
`5.3.1.1.1
`Control channels are used for transfer of control plane information only. The control channels offered by MAC are:
`
`- Broadcast Control Channel (BCCH)
`
` A downlink channel for broadcasting system control information.
`
`- Paging (and Notification) Control Channel (P(N)CCH)
`
` A downlink channel that transfers paging information (and also notifications for MBMS FFS). This channel is
`used when the network does not know the location cell of the UE.
`
`- Common Control Channel (CCCH)
`
`
`
`FFS: This channel is used by the UEs having no RRC connection with the network (need is FFS depending on
`whether the access mechanism is contained in L1. If RACH is visible as a transport channel, CCCH would be
`used by the UEs when accessing a new cell or after cell reselection).
`
`- Multicast Control Channel (MCCH)
`
`3GPP
`
`Ex. 1018 / Page 13 of 26
`
`

`

`
`Release 7
`
`14
`
`3GPP TR 25.813 V0.6.0 (2006-03)
`
`
`
`FFS whether it is distinct from CCCH: a point-to-multipoint downlink channel used for transmitting MBMS
`scheduling and control information from the network to the UE, for one or several MTCHs. After establishing
`RRC connection this channel is only used by UEs that receive MBMS. (Note: old MCCH+MSCH).
`
`- Dedicated Control Channel (DCCH)
`
` A point-to-point bi-directional channel that transmits dedicated control information between a UE and the
`network. Used by UEs having an RRC connection.
`
`Traffic Channels
`5.3.1.1.2
`Traffic channels are used for the transfer of user plane information only. The traffic channels offered by MAC are:
`
`- Dedicated Traffic Channel (DTCH)
`
` A Dedicated Traffic Channel (DTCH) is a point-to-point channel, dedicated to one UE, for the transfer of user
`information. A DTCH can exist in both uplink and downlink.
`
`- Multicast Traffic Channel (MTCH)
`
` A point-to-multipoint downlink channel for transmitting traffic data from the network to the UE. (Note: Includes
`Rel 6/7 MTCH)
`
`Mapping between logical channels and transport channels
`5.3.1.2
`The figure below depicts the mapping between logical and transport channels (in grey the items for FFS):
`
`Figure 5.3.1.2: Mapping between logical channels and transport channels
`
`
`
`Mapping in Uplink
`5.3.1.2.1
`In Uplink, the following connections between logical channels and transport channels exist:
`
`- CCCH can be mapped to RACH; (FFS if access procedure is not contained within L1);
`
`- CCCH can be mapped to Uplink SCH; (FFS: if just a transient (random) ID is assigned for the resource request,
`the actual e.g. RRC Connection Request message has still to contain a UE identifier and therefore such message
`is considered to be a CCCH message, even if it’s transported on the UL_SCH. Also the UE is not in connected
`mode so far);
`
`- DCCH can be mapped to Uplink SCH;
`
`- DTCH can be mapped to Uplink SCH.
`
`Mapping in Downlink
`5.3.1.2.2
`In Downlink, the following connections between logical channels and transport channels exist:
`
`3GPP
`
`Ex. 1018 / Page 14 of 26
`
`

`

`
`Release 7
`
`15
`
`3GPP TR 25.813 V0.6.0 (2006-03)
`
`- BCCH can be mapped to BCH;
`
`- PCCH can be mapped to PCH;
`
`- CCCH can be mapped to Downlink SCH (FFS if CCCH exists);
`
`- DCCH can be mapped to Downlink SCH;
`
`- DTCH can be mapped to Downlink SCH;
`
`- MTCH can be mapped to Downlink SCH; (FFS if a separate MCH does not exist)
`
`- MTCH can be mapped to MCH; (FFS if a separate MCH exists)
`
`- MCCH can be mapped to Downlink SCH; (FFS if a separate MCCH exist)
`
`- MCCH can be mapped to MCH. (FFS if a separate MCCH and MCH exist)
`
`Services and Functions
`5.3.1.3
`The main functions of MAC include:
`
`- Mapping between logical channels and transport channels;
`
`- Multiplexing/demultiplexing of upper layer PDUs belonging to one or different radio bearers into/from transport
`blocks (TB) delivered to/from the physical layer on transport channels;
`
`- Traffic volume measurement reporting;
`
`- Error Correction through HARQ;
`
`- Priority handling between data flows of one UE;
`
`- Priority handling between UEs by means of dynamic scheduling;
`
`- Transport format selection;
`
`- Mapping of Access Classes to Access Service Classes (FFS for RACH).
`
`- Segmentation (FFS);
`
`- Padding (FFS);
`
`- Flow Control (FFS between aGW and eNB);
`
`- Transfer of upper layer PDUs supporting AM, UM or TM data transfer;
`
`- Error Correction through ARQ;
`
`-
`
`In-sequence delivery of upper layer PDUs;
`
`- Duplicate Detection;
`
`- Protocol error detection and recovery;