3GPP TS V ( )

Transcription

1 Technical Specification 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Medium Access Control (MAC) protocol specification (Release 10) The present document has been developed within the 3 rd Generation Partnership Project ( TM ) and may be further elaborated for the purposes of. The present document has not been subject to any approval process by the Organisational Partners and shall not be implemented. This Specification is provided for future development work within only. The Organisational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the TM system should be obtained via the Organisational Partners' Publications Offices.

2 2 Keywords UMTS, radio Postal address support office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: Fax: Internet 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. 2011, Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved. UMTS is a Trade Mark of ETSI registered for the benefit of its members is a Trade Mark of ETSI registered for the benefit of its Members and of the Organizational Partners LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the Organizational Partners GSM and the GSM logo are registered and owned by the GSM Association

3 3 Contents Foreword Scope References Definitions and abbreviations Definitions HS-DSCH Specific Definitions E-DCH Specific Definitions General FDD DTX-DRX and HS-SCCH less Specific definitions (FDD only) HS-DSCH/E-DCH SPS Specific definitions (1.28 Mcps TDD only) Dual Cell E-DCH Specific definitions (FDD only) Abbreviations General Objective MAC architecture MAC Entities MAC-b Traffic Related Architecture - UE Side MAC-c/sh/m entity UE Side MAC-d entity UE Side MAC-hs entity UE Side MAC-e/es entity UE Side MAC-ehs entity UE Side MAC-i/is entity UE Side Traffic Related Architecture - UTRAN Side MAC-c/sh/m entity UTRAN Side MAC-d entity UTRAN Side MAC-hs entity UTRAN Side MAC-es entity UTRAN Side MAC-e entity UTRAN Side MAC-ehs entity UTRAN Side MAC-is entity UTRAN Side MAC-i entity UTRAN Side Channel structure Transport channels Logical Channels Logical channel structure Control Channels Traffic Channels Services provided to upper layers Description of Services provided to upper layers Functions Description of the MAC functions Relation between MAC Functions and Transport Channels Relation between MAC Functions and Transport Channels in UTRAN Relation of MAC Functions and Transport Channels in UE Services expected from physical layer Elements for layer-to-layer communication Primitives between layers 1 and Primitives Parameters... 52

4 4 8.2 Primitives between MAC and RLC Primitives Parameters Primitives between MAC and RRC Primitives Parameters Elements for peer-to-peer communication Protocol data units General MAC PDU (not HS-DSCH or E-DCH) MAC-d PDU (HS-DSCH) MAC PDU (HS-DSCH) MAC PDU (E-DCH) Formats and parameters MAC PDU: Parameters of the MAC PDU header (not HS-DSCH or E-DCH) and MAC-d PDU header (HS-DSCH and E-DCH) MAC header for DTCH and DCCH (not mapped on HS-DSCH or E-DCH) a MAC-d Header for DTCH and DCCH (mapped on HS-DSCH) b MAC-d Header for DTCH and DCCH (mapped on E-DCH) c MAC-d or MAC-c headers for DTCH and DCCH (mapped on HS-DSCH, FDD and 1.28 Mcps TDD only) MAC header for BCCH MAC header for PCCH MAC header for CCCH MAC Header for CTCH MAC Header for SHCCH MAC PDU: Parameters of the MAC header (HS-DSCH) MAC header for DTCH and DCCH Signalling of Transport Block size for HS-DSCH Transport block size for FDD Transport block size for 3.84 Mcps TDD a Transport block size for 7.68 Mcps TDD Transport block size for 1.28 Mcps TDD MAC PDU: Parameters of the MAC header (E-DCH) MAC-es header parameters MAC-e header parameters MAC-is header parameters MAC-i header parameters Signaling of control information for FDD E-DCH HARQ information DL Scheduling information Relative Grants Absolute Grant UL Scheduling information Happy Bit Scheduling Information Transport block size Signaling of control information for TDD E-DCH HARQ information DL Scheduling information Absolute Grant UL Scheduling Information Transport block size Mcps TDD Transport Block Size Mcps TDD Transport Block Size Mcps TDD Transport Block Size Timing Advance and Synchronisation (3.84/7.68 Mcps TDD only) Unsynchronised Handover Synchronisation Timing Advance Request Timing Advance Response

5 5 10 Handling of unknown, unforeseen and erroneous protocol data Specific functions Traffic volume measurement for dynamic radio bearer control Control of RACH transmissions and Enhanced Uplink in CELL_FACH state and Idle mode transmissions Access Service Class selection Control of RACH transmissions for FDD mode A Control of Enhanced Uplink in CELL_FACH state and Idle mode for FDD mode Control of RACH transmissions for TDD Control of RACH transmissions for 3.84 Mcps TDD and 7.68 Mcps TDD Control of E-RUCCH transmissions Control of RACH Transmissions for 1.28 Mcps TDD Control of E-RUCCH transmissions Access Service Class selection Void Void Transport format combination selection in UE (non E-DCH) Ciphering Control of HS-DSCH transmission and reception Network operation Scheduler HARQ entity HARQ process UE operation HARQ Entity HARQ process Reordering entity Definitions Reordering functionality Disassembly entity MAC-hs Reset Reconfiguration of MAC-hs parameters HARQ procedure for HS-SCCH less operation (FDD only) HARQ procedure for HS-DSCH SPS operation (1.28 Mcps TDD only) Network operation Scheduler HARQ entity HARQ process UE operation HARQ Entity HARQ process Disassembly entity Reordering queue distribution entity Reordering entity Definitions Reordering functionality Reassembly unit Demultiplexing entity MAC-ehs Reset Reconfiguration of MAC-ehs parameters HARQ procedure for HS-SCCH less operation (FDD only) HARQ procedure for HS-DSCH SPS operation (1.28 Mcps TDD only) HS-DSCH Provided Bit Rate measurement Control of E-DCH transmission and reception (FDD) UE operation HARQ Operation HARQ entity HARQ process Multiplexing and TSN setting entity TSN setting process operation a Segmentation entity

6 Serving Grant Update Baseline Procedure Handling at start of E-DCH transmission Handling at serving cell change Handling at TTI change Higher Layer Signalling Handling in UE DTX Cycle E-TFC Selection Happy Bit Setting Scheduling Information reporting Report Triggering when SG = Zero_Grant or all processes are deactivated Report Triggering when SG <> Zero_Grant and at least one process is activated MAC-es/e Reset Monitoring of Absolute and Relative Grant Channels Release of common E-DCH resources (FDD only) Node B operation HARQ Operation HARQ entity HARQ process De-multiplexing Scheduler E-DCH Provided Bit Rate measurement Determination of UE-ID (FDD only) and collision resolution RNC operation Re-ordering entity for DTCH/DCCH transmission Re-ordering and CRC entity for CCCH transmission Control of E-DCH transmission and reception (TDD) UE operation HARQ Operation HARQ entity HARQ process Multiplexing and TSN setting entity a Segmentation entity Receiving a Grant E-TFC Selection a Scheduling Information reporting (3.84/7.68 Mcps TDD only) Scheduling Information reporting (1.28 Mcps TDD only) a Cell Reselection Indication in CELL_FACH state (1.28 Mcps TDD only) b Common E-RNTI selection in CELL_FACH state and idle mode (1.28 Mcps TDD only) MAC-es/e Reset (1.28 Mcps TDD only) Node B operation HARQ Operation HARQ entity HARQ process De-multiplexing Scheduler E-DCH Provided Bit Rate measurement RNC operation Re-ordering entity for DTCH/DCCH transmission Re-ordering entity for CCCH transmissio (1.28 Mcps TDD only) Annex A (normative): HS-DSCH Transport Block Size Table for FDD Annex B (normative): E-DCH Transport Block Size Tables for FDD B.1 2ms TTI E-DCH Transport Block Size Table B.2 2ms TTI E-DCH Transport Block Size Table B.2a 2ms TTI E-DCH Transport Block Size Table B.2b 2ms TTI E-DCH Transport Block Size Table B.3 10ms TTI E-DCH Transport Block Size Table B.4 10ms TTI E-DCH Transport Block Size Table

7 7 Annex BA (normative): E-DCH Transport Block Size Tables for 3.84 Mcps TDD BA.1 10ms TTI E-DCH Transport Block Size Table Annex BB (normative): E-DCH Transport Block Size Tables for 7.68 Mcps TDD BB.1 10ms TTI E-DCH Transport Block Size Table Annex BC (normative): E-DCH Transport Block Size Tables for 1.28 Mcps TDD BC.1 5ms TTI E-DCH Transport Block Size Table Annex C (informative): Pseudo-Code for E-TFC Selection (FDD) Annex CA (informative): Pseudo-Code for E-TFC Selection (TDD) Annex D (informative): Change history

8 8 Foreword This Technical Specification (TS) has been produced by the 3 rd Generation Partnership Project (). 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.

9 9 1 Scope The present document specifies the MAC protocol. The specification describes: - MAC architecture; - MAC entities; - channel structure; - services provided to upper layers; - MAC functions; - services expected from the physical layer; - elements for layer-to-layer communication including primitives between MAC and RLC; - elements for peer-to-peer communication; - protocol data units, formats and parameters; - elementary procedures. 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. In the case of a reference to a 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] TR : "Vocabulary for Specifications". [2] TS : "Radio Interface Protocol Architecture". [3] TS : "Services provided by the Physical Layer". [4] TS : "Interlayer Procedures in Connected Mode". [5] TS : "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode". [6] TS : "RLC Protocol Specification". [7] TS : "Radio Resource Control (RRC); protocol specification". [8] TR : "Guidelines and Principles for Protocol Description and Error Handling". [9] TR : "Vocabulary for the UTRAN". [10] TS : "Security architecture". [11] TS : "UTRAN Iur Interface User Plane Protocols for Common Transport Channel Data Streams".

10 10 [12] TS : "Requirements for support of radio resource management (FDD)". [13] TS : "Physical layer procedures (FDD)". [14] TS : "Requirements for support of radio resource management (TDD)". [15] TS : "Cryptographic Algorithm Requirements". [16] TS : "Multiplexing and Channel Coding (FDD)". [17] TS : "Physical layer - Measurements (FDD)". [18] TS : "Physical layer procedures (TDD)". [19] TS : "Multiplexing and Channel Coding (TDD)". [20] TS : "Physical layer Measurements (TDD)". [21] TS "Physical Channels and Mapping of Transport Channels onto Physical Channels (TDD)" [22] TS : "Spreading and modulation (FDD)". [23] TS : "UE Radio Access Capabilities". [24] TS : "Physical channels and mapping of transport channels onto physical channels (FDD)" 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given below and in [9] and [1] apply HS-DSCH Specific Definitions E-DCH Specific Definitions General E-DCH: The Enhanced Dedicated Channel (E-DCH) is an uplink transport channel. HARQ profile: One HARQ profile consists of a power offset attribute and maximum number of transmissions. For 1.28 Mcps TDD, it also includes a retransmission timer attribute. Power offset attribute (FDD): This represents the power offset between E-DPDCH(s) and reference E-DPDCH power level for a given E-TFC. This power offset attribute is set to achieve the required QoS in this MAC-d flow when carried alone in a MAC-e or MAC-i PDU and subsequently in the corresponding CCTrCh of E-DCH type. Details on the mapping on Beta factors can be found in [13]. The reference E-DPDCH power offset is signalled to the UE for one (or several) reference E-TFC(s) (see details in subclause 11.1). Power offset attribute (TDD): The power offset attribute is set to achieve the required QoS in this MAC-d flow when carried alone in a MAC-e or MAC-i PDU and subsequently in the corresponding CCTrCh of E-DCH type. Details on the power offset can be found in [18]. Primary Absolute Grant: Absolute Grant received with the primary E-RNTI. Note that the primary E-RNTI is the only E-RNTI for TDD. Serving E-DCH cell: Cell from which the UE receives Absolute Grants from the Node-B scheduler. A UE has one Serving E-DCH cell.

11 11 Serving_Grant (FDD): The state variable Serving_Grant indicates the maximum E-DPDCH to DPCCH power ratio that the UE is allowed to use for scheduled data in the following transmission. The value in the appropriate state variable will be provided to the E-TFC selection function to help in selecting the best format for the upcoming transmission. Possible values are: "Zero_Grant" and numerical values. The DPCCH power assumed for the Serving_Grant in a compressed frame is the actual DPCCH power in the compressed frame minus 10Log 10 (N pilot,n /N pilot,c ) as defined in [13]. Serving_Grant (TDD): The state variable Serving_Grant indicates the power ratio of maximum E-PUCH power level per TDD resource unit relative to a reference E-PUCH power level P e-ref that the UE is allowed to use for scheduled data on the physical resources associated with the E-AGCH grant. P e-ref is defined as the calculated E-PUCH transmit power (P E-PUCH ) in [18] with e=0. The value in the appropriate state variable will be provided to the E-TFC selection function to help in selecting the best format for the upcoming transmission. Possible values are: "Zero_Grant" and numerical values. UL Common MAC Flow(1.28 Mcps TDD): an UL Common MAC Flow is a flow of MAC-c PDU mapped to E-DCH configured for UEs in Cell_FACH state and IDLE mode FDD Active Process: HARQ process for which Scheduling Grant are applicable, i.e. scheduled data can be sent. AG_Timer: This timer is set to one HARQ RTT (40ms in the case of 10ms TTI, 16ms in the case of 2ms TTI). Common E-DCH resource: Common E-DCH resources are under direct control of the Node B and are shared by UEs in CELL_FACH state and IDLE mode. E-DCH active set: The set of cells which carry the E-DCH for one UE. For FDD, in CELL_FACH state and Idle mode, the E-DCH active set consists of the Serving E-DCH cell only. Inactive Process: HARQ process for which Scheduling Grants are not applicable, i.e. scheduled data cannot be sent. INACTIVE: Absolute Grant value that can be sent by the serving cell's scheduler on the E-AGCH to deactivate a process or to switch the UE to its secondary E-RNTI. In CELL_FACH state, this absolute grant value is used to release a common E-DCH resource. Lowest Configured Serving Grant Value: The serving grant value indicated by index 0 of the SG table in use. Maximum_Serving_Grant: The variable Maximum_Serving_Grant indicates the maximum E-DPDCH to DPCCH power ratio that the UE is allowed to use for scheduled data while the timer Non_Serving_RG_Timer has not expired. Maximum number of re-transmissions, Maximum number of transmissions: Maximum number of re-transmissions = maximum number of transmissions - 1. Both these notations are used. Minimum_Grant: The value Minimum_Grant corresponds to the minimum E-DPDCH to DPCCH power ratio that the UE considers. This value is in index 0 of the configured scheduling grant table described in subclause Non-serving E-DCH RL or Non-serving RL: Cell which belongs to the E-DCH active set but does not belong to the Serving E-DCH RLS and from which the UE can receive one Relative Grant. The UE can have zero, one or several Non-serving E-DCH RL(s). Non_Serving_RG_Timer: This timer is set to one HARQ RTT (40ms in the case of 10ms TTI, 16ms in the case of 2ms TTI). Primary Absolute Grant: Absolute Grant received with the primary E-RNTI. Primary_Grant_Available: This state variable is a Boolean, indicating whether the UE s serving grant is only affected by Primary Absolute Grants and Relative Grants (i.e. not by Secondary Absolute Grants). Primary Uplink Frequency: If a single uplink frequency is configured for the UE, then it is the primary uplink frequency. In case more than one uplink frequencies are configured for the UE, then the primary uplink frequency is the frequency on which the E-DCH corresponding to the serving E-DCH cell associated with the serving HS-DSCH cell is transmitted. The association between a pair of uplink and downlink frequencies is indicated by higher layers. reference_etpr: The state variable reference_etpr holds the E-DPDCH to DPCCH power ratio used as reference for relative grant commands. This variable is set to the E-DPDCH to DPCCH power ratio used for the E-TFC selected

12 12 for the previous TTI on this HARQ process, calculated using the amplitude ratios prior to the quantization according to subclause B.2.3 or B.2.4 of [13], excluding non-scheduled transmissions, excluding any scaling applied according to subclause of [13] and is obtained from the physical layer. In case no scheduled transmission took place on a HARQ process in the previous TTI, reference_etpr shall be set to Minimum_Grant for this HARQ process. reference_etpr2: The state variable reference_etpr2 holds the E-DPDCH to DPCCH power ratio used as reference for non serving relative grant commands. This variable is set to the previously stored reference_etpr on this HARQ process when the reference_etpr is updated with a new value. Secondary Absolute Grant: Absolute Grant received with the secondary E-RNTI. Serving E-DCH RLS or Serving RLS: Set of cells which contains at least the Serving E-DCH cell and from which the UE can receive and combine one Relative Grant. The UE has only one Serving E-DCH RLS. For FDD, in CELL_FACH state and Idle mode, the Serving E-DCH RLS or Serving RLS contains the Serving E-DCH cell only, from which the UE can receive one Relative Grant. Stored_Secondary_Grant: This state variable is used to store the value derived from the last received Secondary Absolute Grant Value. Possible values are: "Zero_Grant" and numerical values. UL Common MAC Flow: an UL Common MAC Flow is a flow of MAC-c PDU mapped to E-DCH configured for UEs in Cell_FACH state and IDLE mode DTX-DRX and HS-SCCH less Specific definitions (FDD only) MAC DTX cycle: Defines the pattern of time instances where the start the uplink E-DCH transmission after inactivity is allowed. MAC Inactivity Threshold: times. E-DCH inactivity time after which the UE can start E-DCH transmission only at given UE DTX DRX Offset: Uplink DPCCH burst pattern and HS-SCCH reception pattern offset in subframes. HS-SCCH less mode of operation: HS-SCCH less mode of operation is enabled when the variable HS_SCCH_LESS_STATUS defined in [7] is set to TRUE. Inactivity Threshold for UE Grant Monitoring: Determines the number of E-DCH TTIs after an E-DCH scheduled transmission during which the UE is required to monitor the full E-AGCH transmissions from the serving radio link and the full E-RGCH(s) from all the cells in the E-DCH active set. Inactivity Threshold for UE DTX cycle 2: Defines a number of consecutive E-DCH TTIs without an E-DCH transmission, after which the UE shall immediately move from UE_DTX_cycle_1 to using UE_DTX_cycle_2. Default-SG-in-DTX-Cycle-2: Defines the default E-DCH Serving Grant used in the case when the UE moves from UE DTX cycle 1 to UE DTX cycle 2 after Inactivity Threshold for UE DTX cycle 2 triggers HS-DSCH/E-DCH SPS Specific definitions (1.28 Mcps TDD only) HS-DSCH SPS operation: HS-DSCH SPS operation is enabled when the variable HS_DSCH_SPS_STATUS defined in [7] is set to TRUE. HS-DSCH SPS resources: Defines the downlink physical resources in term of timeslots and codes on which the first HS-DSCH transmission of transport blocks is performed without the accompanying HS-SCCH and HARQ retransmission of the first HS-DSCH transmission are accompanied by HS-SCCH. E-DCH SPS operation: E-DCH SPS operation is enabled when the variable E_DCH_SPS_STATUS defined in [7] is set to TRUE. E-DCH SPS resources: Defines the uplink physical resources in term of granted timeslots, codes and power on which the UE may transmit transport blocks without receiving other grants on E-AGCH.

13 Dual Cell E-DCH Specific definitions (FDD only) Activated Uplink Frequency: For a specific UE, an uplink frequency is said to be activated if the UE is allowed to transmit on that frequency. The primary uplink frequency is always activated when configured while a secondary uplink frequency has to be activated by means of an HS-SCCH order in order to become activated. Configured Uplink Frequency: For a specific UE, an uplink frequency is said to be configured if the UE has received all relevant information from RRC in order to perform transmission on that frequency. Secondary Uplink Frequency: A secondary uplink frequency is a frequency on which an E-DCH corresponding to a serving E-DCH cell associated with a secondary serving HS-DSCH cell is transmitted. The association between a pair of uplink and downlink frequencies is indicated by higher layers. Secondary E-DCH Active Set: The set of cells on the secondary downlink frequency where E-DCH is carried for one UE. Secondary Serving E-DCH cell: Cell from which the UE can receive Absolute Grants from the Node-B scheduler on the secondary downlink. A UE has one configured Serving E-DCH cell on the secondary uplink frequency. Secondary Serving E-DCH RLS or Secondary Serving RLS: The set of cells which contains at least the Secondary Serving E-DCH cell and from which the UE can receive and combine one Relative Grant. A UE can have zero or one Secondary Serving E-DCH RLS. Secondary Non-serving E-DCH RL or Secondary Non-serving RL:The cell which belongs to the Secondary E-DCH active set but does not belong to the Secondary Serving E-DCH RLS and from which the UE in CELL_DCH can receive one Relative Grant. The UE can have zero, one or several Secondary Non-serving E-DCH RL(s). 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AG Absolute Grant ASC Access Service Class BCCH Broadcast Control Channel BCH Broadcast Channel C- Control- CCCH Common Control Channel DCCH Dedicated Control Channel DCH Dedicated Channel DL Downlink DSCH Downlink Shared Channel DTCH Dedicated Traffic Channel E-AGCH E-DCH Absolute Grant Channel E-DCH Enhanced Dedicated Transport Channel E-DPCCH E-DCH Dedicated Physical Control Channel (FDD only) ENI E-UCCH Number Indication (1.28Mcps TDD only) E-HICH E-DCH HARQ Acknowledgement Indicator Channel E-PUCH Enhanced Uplink Physical Channel (TDD only) E-RGCH E-DCH Relative Grant Channel E-RGCH E-DCH Relative Grant Channel (FDD only) E-RNTI E-DCH Radio Network Temporary Identifier E-RUCCH E-DCH Random Access Uplink Control Channel (TDD only) E-TFC E-DCH Transport Format Combination E-TFCI E-DCH Transport Format Combination Indicator E-UCCH E-DCH Uplink Control Channel (TDD only) FACH Forward Link Access Channel FDD Frequency Division Duplex HARQ Hybrid Automatic Repeat Request HCSN HS-SCCH Cyclic Sequence Number HSDPA High Speed Downlink Packet Access HS-DSCH High Speed Downlink Shared Channel L1 Layer 1 (physical layer)

14 14 L2 Layer 2 (data link layer) L3 Layer 3 (network layer) MAC Medium Access Control MBMS Multimedia Broadcast Multicast Service MCCH MBMS point-to-multipoint Control Channel MTCH MBMS point-to-multipoint Traffic Channel MSCH MBMS point-to-multipoint Scheduling Channel PCCH Paging Control Channel PCH Paging Channel PDU Protocol Data Unit PHY Physical layer PhyCH Physical Channels RACH Random Access Channel RG Relative Grant RLC Radio Link Control RLS Radio Link Set RNC Radio Network Controller RNS Radio Network Subsystem RNTI Radio Network Temporary Identity RRC Radio Resource Control RSN Retransmission Sequence Number SAP Service Access Point SDU Service Data Unit SHCCH Shared Channel Control Channel SRNC Serving Radio Network Controller SRNS Serving Radio Network Subsystem TDD Time Division Duplex TFCI Transport Format Combination Indicator TFI Transport Format Indicator TSN Transmission Sequence Number U- User- UE User Equipment UL Uplink UMTS Universal Mobile Telecommunications System USCH Uplink Shared Channel UTRA UMTS Terrestrial Radio Access UTRAN UMTS Terrestrial Radio Access Network 4 General 4.1 Objective The objective is to describe the MAC architecture and the different MAC entities from a functional point of view. 4.2 MAC architecture The description in this subclause is a model and does not specify or restrict implementations. According to the RRC functions the RRC is generally in control of the internal configuration of the MAC. Both MAC-hs and MAC-ehs are responsible for handling the data transmitted on the HS-DSCH. Furthermore they are responsible for the management of the physical resources allocated to HS-DSCH. Upper layers configure which of the two entities, MAC-hs or MAC-ehs, is to be applied to handle HS-DSCH functionality. Both MAC-e/es and MAC-i/is are responsible for handling the data transmitted on the E-DCH. Upper layers configure which of the two entities, MAC-e/es or MAC-i/is, is to be applied to handle E-DCH functionality.

15 MAC Entities The diagrams that describe the MAC architecture are constructed from MAC entities. The entities are assigned the following names. - MAC-b is the MAC entity that handles the following transport channels: - broadcast channel (BCH) - MAC-c/sh/m, is the MAC entity that handles the following transport channels: - paging channel (PCH) - forward access channel (FACH) - random access channel (RACH) - downlink shared channel (DSCH). The DSCH exists only in TDD mode. - uplink shared channel (USCH). The USCH exists only in TDD mode. - MAC-d is the MAC entity that handles the following transport channels: - dedicated transport channel (DCH) - MAC-hs/ehs is the MAC entity that handles the following transport channels: - high speed downlink shared channel (HS-DSCH) - MAC-m is the MAC entity that handles the following transport channels: - forward access channel (FACH). - MAC-e/es and MAC-i/is are the MAC entities that handle the following transport channels: - enhanced dedicated transport channel (E-DCH). The exact functions completed by the entities are different in the UE from those completed in the UTRAN. NOTE: When a UE is allocated resources for exclusive use by the bearers that it supports the MAC-d entities dynamically share the resources between the bearers and are responsible for selecting the TFI/ TFCI that is to be used in each transmission time interval MAC-b The following diagram illustrates the connectivity of the MAC-b entity in a UE and in each cell of the UTRAN. MAC-b represents the control entity for the broadcast channel (BCH). There is one (current cell) or multiple (current and neighbour cells) MAC-b entities in each UE and one MAC-b in the UTRAN for each cell. The MAC Control SAP is used to transfer Control information to MAC-b. The MAC-b entity is located in the Node B.

16 16 BCCH Mac Control MAC-b BCH Figure : UE side and UTRAN side architecture Traffic Related Architecture - UE Side Figure illustrates the connectivity of MAC entities. The MAC-c/sh/m controls access to all common transport channels, except the HS-DSCH transport channel and the E- DCH transport channel (FDD and 1.28Mcps TDD only). The MAC-d controls access to all dedicated transport channels, to MAC-c/sh/m and MAC-hs/ehs. The MAC-c/sh/m controls access to MAC-is/i. (FDD and 1.28Mcps TDD only for UEs in CELL_FACH state and Idle mode). The MAC-hs/ehs handles the HSDPA specific functions and controls access to the HS-DSCH transport channel. Upper layers configure which of the two entities, MAC-hs or MAC-ehs, is to be applied to handle HS-DSCH functionality. The MAC-e/es or MAC-i/is controls access to the E-DCH transport channel. Upper layers configure which of the two entities, MAC-e/es or MAC-i/is, is to be applied to handle E-DCH functionality. In case of selective combining of MTCH channels from multiple cells, the MAC-m controls access to the FACH transport channels used to carry MTCH and MSCH. In the downlink, if logical channels of dedicated type are mapped to common transport channels then MAC-d receives the data from MAC-c/sh/m or MAC-hs/ehs via the illustrated connection between the functional entities. In the downlink, if logical channels of common type are mapped to HS-DSCH then MAC-c/sh/m receives the data from MAC-ehs via the illustrated connection between the functional entities (FDD and 1.28 Mcps TDD only). In the uplink, if logical channels of dedicated type are mapped to common transport channels then MAC-d submits the data to MAC-c/sh/m and MAC-is/i via the illustrated connection between the functional entities. The mapping of logical channels on transport channels depends on the multiplexing that is configured by RRC. The MAC Control SAP is used to transfer Control information to each MAC entity. The associated signalling shown in the figure illustrates the exchange of information between layer 1 and layer 2 provided by primitives shown in [3].

17 17 MTCH MSCH MTCH MSCH MCCH PCCH BCCH CCCH CTCH SHCCH ( TDD only ) MAC Control DCCH DTCH DTCH MAC-d MAC-es / MAC-e or MAC-is / MAC-i MAC-m MAC-hs/ MAC-ehs (FDD and 1.28 Mcps TDD only, MAC-ehs only ) MAC-c/sh/m Associated Downlink Signalling E-DCH Associated Uplink Signalling FACH Associated Downlink Signalling HS-DSCH Associated Uplink Signalling PCH FACH FACH RACH USCH USCH DSCH ( TDD only ) ( TDD only ) DSCH ( TDD only ) ( TDD only ) DCH DCH Figure : UE side MAC architecture MAC-c/sh/m entity UE Side Figure shows the UE side MAC-c/sh/m entity. The following functionality is covered: - TCTF MUX: - this function represents the handling (insertion for uplink channels and detection and deletion for downlink channels) of the TCTF field in the MAC header, and the respective mapping between logical and transport channels. The TCTF field indicates the common logical channel type, or if a dedicated logical channel is used; - add/read UE Id: - the UE Id is added for RACH transmissions; - the UE Id, when present, identifies data to this UE. - read MBMS Id: - the MBMS Id is read in case of MTCH reception; - the MBMS Id identifies received data to an MBMS service. - UL: TF selection: - in the uplink, the possibility of transport format selection exists. - ASC selection: - For RACH, MAC indicates the ASC associated with the PDU to the physical layer. This is to ensure that RACH messages associated with a given Access Service Class (ASC) are sent on the appropriate signature(s) and time slot(s). MAC also applies the appropriate back-off parameter(s) associated with the given ASC. When sending an RRC CONNECTION REQUEST message, RRC will determine the ASC; in all other cases MAC selects the ASC; - scheduling /priority handling

18 18 - this functionality is used to transmit the information received from MAC-d on RACH based on logical channel priorities. This function is related to TF selection. - TFC selection - transport format and transport format combination selection according to the transport format combination set (or transport format combination subset) configured by RRC is performed, The RLC provides RLC-PDUs to the MAC, which fit into the available transport blocks on the transport channels. There is one MAC-c/sh/m entity in each UE. PCCH SHCCH (TDD only) CCCH CTCH BCCH MCCH MSCH MTCH MTCH MAC Control From MAC-ehs (FDD and 1.28Mcp s TDD only) read MBMS Id add/read UE Id MAC-c/sh/m to MAC d TCTF MUX Scheduling/Priority Handling (1) TFC selection UL: TF selection ASC selection PCH DSCH TDD only DSCH TDD only USCH TDD only USCH TDD only FACH FACH RACH to MAC-is/i Note: Dashed lines are FDD and 1.28Mcps TDD only Figure : UE side MAC architecture / MAC-c/sh/m details b MAC-m entity UE Side Figure b.1 shows the UE side MAC-m entity. The following functionality is covered: - TCTF DEMUX: - this function represents the handling (detection and deletion for downlink channels) of the TCTF field in the MAC header, and the respective mapping between logical and transport channels. The TCTF field indicates the common logical channel type; - read MBMS Id - the MBMS Id is read in case of MTCH reception; - the MBMS Id identifies received data to an MBMS service. The MAC Control SAP is used to transfer control information to MAC-m. If MTCH channels are selectively combined, the MAC-m entity exists in the UE. Otherwise, the MAC-m entity does not exist. In case of selective combining of MTCH channels from multiple cells, there are one MAC-c/sh/m for the current cell and one MAC-m entity for each neighboring cell in the UE.

19 19 MAC-Control MTCH MTCH MSCH read MBMS-ID TCTF DEMUX MAC-m FACH FACH Figure b.1: UE side MAC architecture / MAC-m details MAC-d entity UE Side Figure shows the UE side MAC-d entity. The following functionality is covered: - Transport Channel type switching - Transport Channel type switching is performed by this entity, based on decision taken by RRC. This is related to a change of radio resources. If requested by RRC, MAC shall switch the mapping of one designated logical channel between common and dedicated transport channels. - C/T MUX: - The C/T MUX is used when multiplexing of several dedicated logical channels onto one transport channel (other than HS-DSCH) or one MAC-d flow (HS-DSCH) is used. An unambiguous identification of the logical channel is included. If MAC-ehs is configured, C/T MUX toward MAC-ehs is not used. - Ciphering: - Ciphering for transparent mode data to be ciphered is performed in MAC-d. Details about ciphering can be found in [10]. - Deciphering: - Deciphering for ciphered transparent mode data is performed in MAC-d. Details about ciphering can be found in [10]. - UL TFC selection: - Transport format and transport format combination selection according to the transport format combination set (or transport format combination subset) configured by RRC is performed. The MAC-d entity is responsible for mapping dedicated logical channels for the uplink either onto dedicated transport channels or to transfer data to MAC-c/sh/m to be transmitted via common channels. One dedicated logical channel can be mapped simultaneously onto DCH and DSCH in TDD mode. One dedicated logical channel can be simultaneously mapped onto DCH and HS-DSCH. The MAC-d entity has a connection to the MAC-c/sh/m entity. This connection is used to transfer data to the MACc/sh/m to transmit data on transport channels that are handled by MAC-c/sh/m (uplink) or to receive data from transport channels that are handled by MAC-c/sh/m (downlink).

20 20 The MAC-d entity has a connection to the MAC-hs or MAC-ehs entity. This connection is used to receive data from the HS-DSCH transport channel which is handled by MAC-hs or MAC-ehs (downlink). The MAC-d entity has a connection to the MAC-e/es or MAC-i/is entity. This connection is used to transmit data on the E-DCH transport channel which is handled by the MAC-e/es or MAC-i/is (uplink). There is one MAC-d entity in the UE. MAC Control DCCH DTCH DTCH MAC-d Transport Channel Type Switching Deciphering from MAC-ehs C/T MUX from MAC-hs to/from MAC-c/sh to MAC-e/es or to MAC-i/is C/T MUX UL: TFC selection Ciphering DCH DCH Figure : UE side MAC architecture / MAC-d details MAC-hs entity UE Side In the model below the MAC-hs comprises the following entities. In 1.28 Mcps TDD multi-frequency HS-DSCH cell, the associated downlink control channel and uplink control channel pair controlling the HS-DSCH transmission on the certain carrier shall be allocated on the same carrier. The downlink control channel carries the HS-DSCH operation related info and the uplink control channel carries the feedback info from the UE side. - HARQ: The HARQ entity is responsible for handling the MAC functions relating to the HARQ protocol. The HARQ functional entity handles all the tasks that are required for hybrid ARQ. It is responsible for generating ACKs or NACKs. The detailed configuration of the hybrid ARQ protocol is provided by RRC over the MAC-Control SAP. In 1.28 Mcps TDD multi-frequency HS-DSCH cell, multiple HARQ processes are assigned for HS-DSCH operaton on every carrier independently, namely HARQ sub-entity; only one HARQ process is allowed to receive HS-DSCH in one TTI for each carrier. The maximum number of HARQ process per HS-DSCH per TTI on which an HS-DSCH transmission can be received is one. - Reordering Queue distribution: The reordering queue distribution function routes the MAC-hs PDUs to the correct reordering buffer based on the Queue ID.For 1.28 Mcps TDD, the reordering queue distribution function discards the MAC-hs PDU if the N field in MAC-hs header is zero. - Reordering: The reordering entity reorders received MAC-hs PDUs according to the received TSN. MAC-hs PDUs with consecutive TSNs are delivered to the disassembly function upon reception. MAC-hs PDUs are not delivered to the disassembly function if MAC-hs PDUs with lower TSN are missing. There is one reordering entity for each Queue ID configured at the UE.

21 21 - Disassembly: The disassembly entity is responsible for the disassembly of MAC-hs PDUs. When a MAC-hs PDU is disassembled the MAC-hs header is removed, the MAC-d PDUs are extracted and any present padding bits are removed. Then the MAC-d PDUs are delivered to higher layer. The associated signalling shown in the figure illustrates the exchange of information between layer 1 and layer 2 provided by primitives shown in [3]. To MAC-d MAC Control MAC-hs Disassembly Reordering Disassembly Reordering Re-ordering queue distribution HARQ Associated Downlink Signalling HS-DSCH Associated Uplink Signalling Figure : UE side MAC architecture / MAC-hs details MAC Control Carrier 1 To MAC-d MAC-hs Disassembly Disassembly Reording Reording Reording queue distribution HARQ Carrier 1 HARQ Carrier n Associated downlink signalling HS-DSCH Associated uplink signalling Associated downlink signalling HS-DSCH Associated uplink signalling Carrier 1 Carrier n Figure : UE side MAC architecture/mac-hs details (1.28Mcps TDD multi-frequency HS-DSCH operation mode only)

22 MAC-e/es entity UE Side The split between MAC-e and MAC-es in the UE is not detailed. In the model below the MAC-e/es comprises the following entities: - HARQ: The HARQ entity is responsible for handling the MAC functions relating to the HARQ protocol. It is responsible for storing MAC-e payloads and re-transmitting them. The detailed configuration of the hybrid ARQ protocol is provided by RRC over the MAC-Control SAP. - For FDD: The HARQ entity provides the E-TFC, the retransmission sequence number (RSN), and the power offset to be used by L1. Redundancy version (RV) of the HARQ transmission is derived by L1 from RSN, CFN and in case of 2 ms TTI from the sub-frame number. - For TDD: The HARQ entity provides the HARQ process identity, the E-TFC, the retransmission sequence number (RSN) and an indication of the power offset to be used by L1. The redundancy version (RV) of the HARQ transmission is derived by L1 from RSN. RRC signalling can also configure the L1 to use RV=0 for every transmission. - Multiplexing and TSN setting: The multiplexing and TSN setting entity is responsible for concatenating multiple MAC-d PDUs into MAC-es PDUs, and to multiplex one or multiple MAC-es PDUs into a single MAC-e PDU, to be transmitted in the next TTI, as instructed by the E-TFC selection function. It is also responsible for managing and setting the TSN per logical channel for each MAC-es PDU. - E-TFC selection: This entity is responsible for E-TFC selection according to the scheduling information, Relative Grants (FDD only) and Absolute Grants, received from UTRAN via L1 and Serving Grant value signalled through RRC, and for arbitration among the different flows mapped on the E-DCH. The detailed configuration of the E-TFC entity is provided by RRC over the MAC-Control SAP. The E-TFC selection function controls the multiplexing function. - Scheduling Access Control (TDD only): The Scheduling Access Control entity is responsible for routing associated uplink signalling via E-UCCH and MAC-e PDU (in the case that E-DCH resources are assigned) or via E-RUCCH (in the case that no E-DCH resources are assigned). It is also responsible for obtaining and formatting the appropriate information to be carried on E-UCCH/E-RUCCH. NOTE: HARQ process ID and RSN are carried on E-UCCH.

23 23 To MAC-d MAC Control MAC-es/e E-TFC Selection Multiplexing and TSN setting HARQ Associated Scheduling Downlink Signalling (E-AGCH / E-RGCH(s)) Associated ACK/NACK signaling (E-HICH) Associated Uplink Signalling E-TFC (E-DPCCH) Figure a: UE side MAC architecture / MAC-e/es details (FDD) To MAC-d MAC Control E-TFC Selection MAC-es/e Multiplexing and TSN setting Scheduling Access Control HARQ Associated Scheduling Downlink Signalling (E-AGCH ) Associated ACK/NACK signaling (E-HICH) Associated Uplink Signalling E-UCCH Associated Uplink Signalling E-RUCCH Figure b: UE side MAC architecture / MAC-e/es details (TDD) MAC-ehs entity UE Side In the model below the MAC-ehs comprise the following entities, In 1.28 Mcps TDD multi-frequency HS-DSCH cell, the associated downlink control channel and uplink control channel pair controlling the HS-DSCH transmission on the certain carrier shall be allocated on the same carrier. The downlink control channel carries the HS-DSCH operation related info and the uplink control channel carries the feedback info from the UE side.

24 24 - HARQ: The HARQ entity is responsible for handling the HARQ protocol. There shall be one HARQ process per HS- DSCH per TTI for single stream transmission and two HARQ processes per HS-DSCH per TTI for dual stream transmission. There shall be one HARQ entity per HS-DSCH (FDD only). The HARQ functional entity handles all the tasks that are required for hybrid ARQ. It is for example responsible for generating ACKs or NACKs. The detailed configuration of the hybrid ARQ protocol is provided by RRC over the MAC-Control SAP.In 1.28 Mcps TDD multi-frequency HS-DSCH cell, multiple HARQ processes are assigned for HS-DSCH operaton on every carrier independently, namely HARQ sub-entity; only one HARQ process is allowed to receive HS- DSCH in one TTI for each carrier. The maximum number of HARQ process per HS-DSCH per TTI on which an HS-DSCH transmission can be received is one. - Disassembly The disassembly entity disassembles the MAC-ehs PDUs by removing the MAC-ehs header and possible padding. For 1.28 Mcps TDD, the disassembly entity discards the MAC-ehs PDU if the L field in MAC-ehs header is zero. - Reordering queue distribution The reordering queue distribution function routes the received reordering PDUs to correct reordering queues based on the received logical channel identifier. - Reordering: The reordering entity organises received reordering PDUs according to the received TSN. Data blocks with consecutive TSNs are delivered to reassembly entity upon reception. A timer mechanism determines delivery of non-consecutive data blocks to higher layers. There is one reordering entity for each MAC-ehs Queue ID configured at the UE. For the logical channels BCCH and PCCH no re-ordering is applied. - Reassembly: The reassembly entity reassembles segmented MAC-ehs SDUs (corresponding to either MAC-c or MAC-d PDUs) and forwards the MAC PDUs to LCH-ID demultiplexing entity. - LCH-ID demultiplexing: The demultiplexing entity routes the MAC-ehs SDUs to correct logical channel based on the received logical channel identifier. The following is allowed: The MAC-ehs SDUs included in a MAC-ehs PDU can have a different size and a different priority and can be mapped to different priority queues.

25 25 To MAC-d To MAC-c/sh/m MAC Control MAC-ehs LCH-ID Demux LCH-ID Demux LCH-ID Demux Reassembly Reassembly Reassembly Reordering Reordering Reordering Re-ordering queue distribution Disassembly HARQ HARQ Associated Downlink Signalling HS-DSCH Associated Uplink Signalling Associated Downlink Signalling HS-DSCH Associated Uplink Signalling Figure : UE side MAC architecture/mac-ehs details. MAC Control Carrier 1 To MAC-d MAC-ehs LCH-ID Demux LCH-ID Demux Reassembly Reassembly Reording Reording Reording queue distribution Disassembly HARQ Carrier 1 HARQ Carrier n Associated downlink signalling HS-DSCH Associated uplink signalling Associated downlink signalling HS-DSCH Associated uplink signalling Carrier 1 Carrier n Figure : UE side MAC architecture/mac-ehs details (1.28Mcps TDD multi-frequency HS- DSCH operation mode only)

26 MAC-i/is entity UE Side The split between MAC-i and MAC-is in the UE is not detailed. In the model below the MAC-i/is comprises the following entities: - HARQ: The HARQ entity is responsible for handling the MAC functions relating to the HARQ protocol. It is responsible for storing MAC-i payloads and re-transmitting them. The detailed configuration of the hybrid ARQ protocol is provided by RRC over the MAC-Control SAP. - For FDD: There shall be one HARQ entity per E-DCH. The HARQ entity provides the E-TFC, the retransmission sequence number (RSN), and the power offset to be used by L1. Redundancy version (RV) of the HARQ transmission is derived by L1 from RSN, CFN and in case of 2 ms TTI from the sub-frame number. - For TDD: There shall be one HARQ entity per E-DCH for 1.28Mcps TDD. The HARQ entity provides the HARQ process identity, the E-TFC, the retransmission sequence number (RSN) and an indication of the power offset to be used by L1. The redundancy version (RV) of the HARQ transmission is derived by L1 from RSN. RRC signalling can also configure the L1 to use RV=0 for every transmission. - Multiplexing and TSN setting: The multiplexing and TSN setting entity is responsible for concatenating multiple MAC-d PDUs into MAC-is PDUs, and to multiplex one or multiple MAC-is PDUs into a single MAC-i PDU, or, for FDD when more than one uplink frequency is activated, one or two MAC-i PDUs, to be transmitted in the next TTI, as instructed by the E-TFC selection function, and for 1.28Mcps TDD when multi-carrier E-DCH operation is activated, one or up to 6 MAC-i PDUs, to be transmitted in the next TTI, as instructed by the E-TFC selection function. It is also responsible for managing and setting the TSN per logical channel for each MAC-is PDU. In FDD and 1.28 Mcps TDD, the multiplexing and TSN setting entity is responsible for multiplexing MAC-c PDUs or segments of MAC-c PDUs into a single MAC-is PDU, and for multiplexing MAC-is PDUs into a single MAC-i PDU, to be transmitted in the next TTI, as instructed by the E-TFC selection function. It is also responsible for managing and setting the TSN for the common control channel for each MAC-is PDU. - Segmentation: The segmentation function is responsible for segmenting MAC-d PDUs and MAC-c PDUs (FDD and 1.28 Mcps TDD only). - CRC Attachment (FDD and 1.28 Mcps TDD only): If segmentation is performed for MAC-c PDUs, a CRC is appended to the MAC-c PDU and segmentation is then performed for the entire MAC-c PDU including CRC. The size of the CRC field is 8 bits and the CRC is calculated as specified in section in [16] or [19]. In the CRC field, see Figure d, the LSB is the rightmost bit and the MSB is the leftmost bit. - Add UE ID (FDD only): In CELL_DCH state, no E-RNTI is included in the MAC-PDU header. In CELL_FACH, the E-RNTI is added in all MAC-i PDUs for DCCH and DTCH transmission at the UE side until the UE receives an E-AGCH with its E-RNTI (through an E-RNTI-specific CRC attachment). In CELL_FACH state and in Idle mode, no E-RNTI is added in MAC-i PDUs for CCCH data transmission. - E-TFC selection: This entity is responsible for E-TFC selection according to the scheduling information, Relative Grants (FDD only) and Absolute Grants, received from UTRAN via L1 and Serving Grant value signalled through RRC, and for arbitration among the different flows mapped on the E-DCH. The detailed configuration of the E-TFC entity is provided by RRC over the MAC-Control SAP. The E-TFC selection function controls the multiplexing function. - ASC selection (FDD and 1.28 Mcps TDD only): At the start of the Enhanced Uplink in CELL_FACH state and Idle mode, MAC-is/i applies the appropriate back-off parameter(s) associated with the given ASC. When sending an RRC CONNECTION REQUEST message, RRC will determine the ASC; in all other cases MAC-is/i selects the ASC. - Scheduling Access Control (TDD only): The Scheduling Access Control entity is responsible for routing associated uplink signalling via E-UCCH and MAC-i PDU (in the case that E-DCH resources are assigned) or via E-RUCCH (in the case that no E-DCH