`
`
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`Technical Specification
`
`3rd Generation Partnership Project;
`Technical Specification Group Radio Access Network;
`MAC protocol specification
`(Release 1999)
`
`
`
`
`
`
`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.
`
`1
`
`

`

`
`
`
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`Technical Specification
`
`3rd Generation Partnership Project;
`Technical Specification Group Radio Access Network;
`MAC protocol specification
`(Release 1999)
`
`
`
`
`
`
`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.
`
`1
`
`

`

`
`Release 1999
`
`2
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`
`
`
`
`
`
`
`
`Keywords
`UMTS, radio
`
`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.
`
`© 2000, 3GPP Organizational Partners (ARIB, CWTS, ETSI, T1, TTA,TTC).
`All rights reserved.
`
`
`3GPP
`
`

`

`
`Release 1999
`
`3
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`Contents
`Foreword............................................................................................................................................................. 5
`1
`Scope ........................................................................................................................................................ 6
`2
`References ................................................................................................................................................ 6
`3
`Definitions and abbreviations ................................................................................................................... 7
`3.1 Definitions ............................................................................................................................................................... 7
`3.2 Abbreviations .......................................................................................................................................................... 7
`4
`General ..................................................................................................................................................... 8
`4.1 Objective ................................................................................................................................................................. 8
`4.2 MAC architecture .................................................................................................................................................... 8
`4.2.1
`MAC Entities ..................................................................................................................................................... 8
`4.2.2
`MAC-b ............................................................................................................................................................... 8
`4.2.3
`Traffic Related Architecture - UE Side.............................................................................................................. 9
`4.2.3.1 MAC-c/sh entity – UE Side ............................................................................................................................... 9
`4.2.3.2 MAC-d entity – UE Side ................................................................................................................................. 11
`4.2.4
`Traffic Related Architecture - UTRAN Side ................................................................................................... 12
`4.2.4.1 MAC-c/sh entity – UTRAN Side ..................................................................................................................... 13
`4.2.4.2 MAC-d entity – UTRAN Side ......................................................................................................................... 14
`4.3 Channel structure ................................................................................................................................................... 15
`4.3.1
`Transport channels ........................................................................................................................................... 15
`4.3.2
`Logical Channels ............................................................................................................................................. 16
`4.3.2.1 Logical channel structure ................................................................................................................................. 16
`4.3.2.2 Control Channels ............................................................................................................................................. 16
`4.3.2.3 Traffic Channels .............................................................................................................................................. 16
`4.3.3
`Mapping between logical channels and transport channels ............................................................................. 17
`5
`Services provided to upper layers .......................................................................................................... 17
`5.1 Description of Services provided to upper layers .................................................................................................. 17
`6
`Functions ................................................................................................................................................ 17
`6.1 Description of the MAC functions ........................................................................................................................ 17
`6.2 Relation between MAC Functions and Transport Channels .................................................................................. 18
`6.2.1
`Relation between MAC Functions and Transport Channels in UTRAN ......................................................... 18
`6.2.2
`Relation of MAC Functions and Transport Channels in UE ........................................................................... 19
`7
`Services expected from physical layer ................................................................................................... 19
`8
`Elements for layer-to-layer communication ........................................................................................... 19
`8.1
`Primitives between layers 1 and 2 ......................................................................................................................... 19
`8.2
`Primitives between MAC and RLC ....................................................................................................................... 19
`8.2.1
`Primitives ......................................................................................................................................................... 19
`8.2.2
`Parameters........................................................................................................................................................ 20
`8.3
`Primitives between MAC and RRC ....................................................................................................................... 21
`8.3.1
`Primitives ......................................................................................................................................................... 21
`8.3.2
`Parameters........................................................................................................................................................ 21
`9
`Elements for peer-to-peer communication ............................................................................................. 22
`9.1
`Protocol data units ................................................................................................................................................. 22
`9.1.1
`General ............................................................................................................................................................. 22
`9.1.2
`MAC Data PDU ............................................................................................................................................... 23
`9.2
`Formats and parameters ......................................................................................................................................... 23
`9.2.1
`MAC Data PDU: Parameters of the MAC header ........................................................................................... 23
`9.2.1.1 MAC header for DTCH and DCCH ................................................................................................................ 25
`9.2.1.2 MAC header for BCCH ................................................................................................................................... 26
`9.2.1.3 MAC header for PCCH .................................................................................................................................... 26
`9.2.1.4 MAC header for CCCH ................................................................................................................................... 26
`9.2.1.5 MAC Header for CTCH .................................................................................................................................. 27
`
`3GPP
`
`

`

`
`Release 1999
`
`4
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`9.2.1.6 MAC Header for SHCCH ................................................................................................................................ 27
`10 Handling of unknown, unforeseen and erroneous protocol data ............................................................ 27
`11
`Elementary procedures ........................................................................................................................... 27
`11.1
`Traffic volume measurement for dynamic radio bearer control....................................................................... 27
`11.2
`Control of RACH transmissions ...................................................................................................................... 29
`11.2.1
`Access Service Class selection ........................................................................................................................ 29
`11.2.2
`Control of RACH transmissions for FDD mode .............................................................................................. 30
`11.2.3
`Control of RACH transmissions for TDD ....................................................................................................... 33
`11.3
`Control of CPCH transmissions for FDD ........................................................................................................ 34
`11.4
`Transport format combination selection in UE ................................................................................................ 38
`11. 5 Ciphering ................................................................................................................................................................. 39
`Annex A (informative): Change history ....................................................................................................... 40
`
`
`3GPP
`
`

`

`
`Release 1999
`
`5
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`Foreword
`This Technical Specification (TS) 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.
`
`3GPP
`
`

`

`
`Release 1999
`
`6
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`Scope
`1
`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.
`
`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.
`
`[1]
`
`[2]
`
`[3]
`
`[4]
`
`[5]
`
`[6]
`
`[7]
`
`[8]
`
`[9]
`
`[10]
`
`[11]
`
`3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
`
`3GPP TS 25.301: "Radio Interface Protocol Architecture".
`
`3GPP TS 25.302: "Services provided by the Physical Layer".
`
`3GPP TS 25.303: "Interlayer Procedures in Connected Mode".
`
`3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected
`Mode".
`
`3GPP TS 25.322: "RLC Protocol Specification".
`
`3GPP TS 25.331: "RRC Protocol Specification".
`
`3GPP TR 25.921: "Guidelines and Principles for Protocol Description and Error Handling".
`
`3GPP TR 25.990: "Vocabulary for the UTRAN".
`
`3GPP TS 33.102: "Security architecture".
`
`3GPP TS 25.425: "UTRAN Iur Interface User Plane Protocols for Common Transport Channel
`Data Streams".
`
`3GPP
`
`

`

`
`Release 1999
`
`7
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`3
`
`Definitions and abbreviations
`
`Definitions
`3.1
`For the purposes of the present document, the terms and definitions given in [9] and [1] apply.
`
`Abbreviations
`3.2
`For the purposes of the present document, the following abbreviations apply:
`
`
`ASC
`BCCH
`BCH
`C-
`CCCH
`CPCH
`DCCH
`DCH
`DL
`DSCH
`DTCH
`FACH
`
`FDD
`L1
`L2
`L3
`MAC
`PCCH
`PCH
`PDU
`PHY
`PhyCH
`RACH
`RLC
`RNC
`RNS
`RNTI
`RRC
`SAP
`SDU
`SHCCH
`SRNC
`SRNS
`TDD
`TFCI
`TFI
`U-
`UE
`UL
`UMTS
`USCH
`UTRA
`UTRAN
`
`Access Service Class
`Broadcast Control Channel
`Broadcast Channel
`Control-
`Common Control Channel
`Common Packet Channel (UL)
`Dedicated Control Channel
`Dedicated Channel
`Downlink
`Downlink Shared Channel
`Dedicated Traffic Channel
`Forward Link Access Channel
`
`Frequency Division Duplex
`Layer 1 (physical layer)
`Layer 2 (data link layer)
`Layer 3 (network layer)
`Medium Access Control
`Paging Control Channel
`Paging Channel
`Protocol Data Unit
`Physical layer
`Physical Channels
`Random Access Channel
`Radio Link Control
`Radio Network Controller
`Radio Network Subsystem
`Radio Network Temporary Identity
`Radio Resource Control
`Service Access Point
`Service Data Unit
`Shared Channel Control Channel
`Serving Radio Network Controller
`Serving Radio Network Subsystem
`Time Division Duplex
`Transport Format Combination Indicator
`Transport Format Indicator
`User-
`User Equipment
`Uplink
`Universal Mobile Telecommunications System
`Uplink Shared Channel
`UMTS Terrestrial Radio Access
`UMTS Terrestrial Radio Access Network
`
`3GPP
`
`

`

`
`Release 1999
`
`8
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`4
`
`General
`
`Objective
`4.1
`The objective is to describe the MAC architecture and the different MAC entities from a functional point of view.
`
`MAC architecture
`4.2
`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.
`
`4.2.1 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, is the MAC entity that handles the following transport channels:
`
`- paging channel (PCH)
`
`-
`
`-
`
`forward access channel (FACH)
`
`random access channel (RACH)
`
`- common packet channel (UL CPCH). The CPCH exists only in FDD mode.
`
`- downlink shared channel (DSCH)
`
`- 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 channels (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.
`
`
`
`4.2.2 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 MAC-b entity 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.
`
`
`
`3GPP
`
`

`

`
`Release 1999
`
`9
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`BCCH
`
`Mac Control
`
`MAC-b
`
`BCH
`
`
`Figure 4.2.2.1: UE side and UTRAN side architecture
`
`
`
`Traffic Related Architecture - UE Side
`4.2.3
`Figure 4.2.3.1 illustrates the connectivity of MAC entities.
`
`The MAC-c/sh controls access to common transport channels.
`
`The MAC-d controls access to dedicated transport channels.
`
`If logical channels of dedicated type are mapped to common channels then MAC-d passes the data to MAC-c/sh 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.
`
`PCCH
`
`BCCH CCCH
`
`CTCH
`
`SHCCH
`( TDD only )
`
`MAC Control
`
`DCCH
`
`DTCH
`
`DTCH
`
`MAC-d
`
`MAC-c/sh
`
`PCH
`
`FACH
`
`FACH RACH
`
`CPCH
`( FDD only )
`
`USCH
`( TDD only )
`
`USCH
`( TDD only )
`
`DSCH
`
`DSCH DCH DCH
`
`
`
`Figure 4.2.3.1: UE side MAC architecture
`
`MAC-c/sh entity – UE Side
`4.2.3.1
`Figure 4.2.3.1.1 shows the UE side MAC-c/sh entity.
`
`3GPP
`
`

`

`
`Release 1999
`
`10
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`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 CPCH and RACH transmissions
`
`the UE Id, when present, identifies data to this UE.
`
`- UL: TF selection:
`
`-
`
`in the uplink, the possibility of transport format selection exists.
`In case of CPCH transmission, a TF is selected based on TF availability determined from status information
`on the CSICH;
`
`- ASC selection:
`
`- For RACH, MAC indicates the ASC associated with the PDU to the physical layer. For CPCH, MAC may
`indicate the ASC associated with the PDU to the Physical Layer. This is to ensure that RACH and CPCH
`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;
`
`-
`
`scheduling /priority handling
`
`-
`
`this functionality is used to transmit the information received from MAC-d on RACH and CPCH 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 entity in each UE.
`
`3GPP
`
`

`

`
`Release 1999
`
`11
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`PCCH
`
`SHCCH (TDD only)
`
`CCCH
`
`CTCH
`
`BCCH
`
`MAC – Control
`
`MAC-c/sh
`
`to MAC –d
`
`TCTF MUX
`
`TFC
`selection
`
`add/read
` UE Id
`
`Scheduling/Priority
`Handling (1)
`
`UL: TF selection
`
`ASC
`selection
`
`ASC
`selection (2)
`
`PCH
`
`DSCH
`
`DSCH
`
`USCH
`TDD only
`
`USCH
`TDD only
`
`FACH
`
`FACH
`
`RACH
`
`CPCH ( FDD only )
`
`DL
`TF
`TFC
`TCTF
`(1)
`
`(2)
`
`Downlink
`Transport Format
`Transport Format Combination
`Target Channel Type Field
`Scheduling /Priority handling is applicable for
`CPCH, details are ffs.
`In case of CPCH, ASC selection may be applicable
`for AP preamble.
`
`UE
`UL
`
`User Equipment
`Uplink
`
`Figure 4.2.3.1.1: UE side MAC architecture / MAC-c/sh details
`
`
`
`MAC-d entity – UE Side
`4.2.3.2
`Figure 4.2.3.2.1 shows the UE side MAC-d entity.
`
`The following functionality is covered:
`
`- Channel switching
`
`- dynamic transport channel type switching is performed by this entity, based on decision taken by RRC. This
`is usually related to a change of radio resources.
`
`- C/T MUX:
`
`-
`
`the C/T MUX is used when multiplexing of several dedicated logical channels onto one transport channel is
`used. An unambiguous identification of the logical channel is included.
`
`- 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.
`
`3GPP
`
`

`

`
`Release 1999
`
`12
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`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 to be transmitted via common channels.
`
`One dedicated logical channel can be mapped simultaneously onto DCH and DSCH;
`
`The MAC-d entity has a connection to the MAC-c/sh entity. This connection is used to transfer data to the MAC-c/sh to
`transmit data on transport channels that are handled by MAC-c/sh (uplink) or to receive data from transport channels
`that are handled by MAC-c/sh (downlink).
`
`There is one MAC-d entity in the UE.
`
`
`
`MAC Control
`
`DCCH DTCH DTCH
`
` MAC-d
`
`C/T MUX
`
`to MAC-c/sh
`
`Channel switching
`
`Deciphering
`
`C/T
` MUX
`
`UL: TFC selection
`
`Ciphering
`
`DCH
`
`DCH
`
`Downlink
`DL
`Transport Format
`TF
`Transport Format Combination
`TFC
`Note1 : For DCH and DSCH different scheduling
`mechanism apply
`
`RNTI
`UE
`UL
`Note 2 :
`Note 3 :
`
`Radio Network Temporary Identity
`User Equipment
`Uplink
`The TFC selection place is under discussion
`Ciphering is performed in MAC-d only for
`transparent RLC mode
`
`
`Figure 4.2.3.2.1: UE side MAC architecture / MAC-d details
`
`
`
`Traffic Related Architecture - UTRAN Side
`4.2.4
`Figure 4.2.4.1 illustrates the connectivity between the MAC entities from the UTRAN side.
`
`It is similar to the UE case with the exception that there will be one MAC-d for each UE and each UE (MAC-d) that is
`associated with a particular cell may be associated with that cell's MAC-c/sh.
`
`MAC-c/sh is located in the controlling RNC while MAC-d is located in the serving RNC.
`
`The MAC Control SAP is used to transfer Control information to each MAC entity belongs to one UE.
`
`3GPP
`
`

`

`
`Release 1999
`
`13
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`PCCH
`
`BCCH
`
`CCCH CTCH
`
`SHCCH
` TDD only
`
`MAC Control
`
` MAC Control
`
`DCCH
`
`DTCH
`
`DTCH
`
`MAC-d
`
`MAC-c/sh
`
`PCH
`
`FACH
`
`FACH RACH
`
`CPCH
`FDD only
`
`USCH
`TDD only
`
`USCH
`TDD only
`
`DSCH
`
`DSCH
`
`Iur or local
`
`DCH DCH
`
`
`
`
`
`Figure 4.2.4.1: UTRAN side MAC architecture
`
`MAC-c/sh entity – UTRAN Side
`4.2.4.1
`Figure 4.2.4.1.1 shows the UTRAN side MAC-c/sh entity. The following functionality is covered:
`
`-
`
`the Scheduling – Priority Handling;
`
`-
`
`this function manages FACH and DSCH resources between the UE's and between data flows according to
`their priority.
`
`- TCTF MUX
`
`-
`
`this function represents the handling (insertion for downlink channels and detection and deletion for uplink
`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;
`
`- UE Id Mux;
`
`-
`
`for dedicated type logical channels, the UE Id field in the MAC header is used to distinguish between UEs;
`
`- TFC selection:
`
`-
`
`in the downlink, transport format combination selection is done for FACH and PCH and DSCHs;
`
`- demultiplex;
`
`-
`
`for TDD operation the demultiplex function is used to separate USCH data from different UEs, i.e. to be
`transferred to different MAC-d entities;
`
`- DL code allocation;
`
`-
`
`this function is used to indicate the code used on the DSCH;
`
`Flow control is provided to MAC-d.
`
`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 entity in the UTRAN for each cell;
`
`3GPP
`
`

`

`
`Release 1999
`
`14
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`P C C H
`
`B C C H
`
`S H C C H
`(T D D o n l y )
`
`C C C H
`
`C T C H
`
`M A C – C o n tr o l
`
`M A C - c / s h
`
`F lo w C o n tr o l
`M A C - c /s h / M A C - d
`
`to M A C – d
`
`T C T F M U X / U E Id M U X
`
`S c h e d u lin g / P r io r ity H a n d lin g / D e m u x
`
` T F C s e le c tio n
`
` T F C s e le c tio n
`
`D L : c o d e
`a llo c a tio n
`
`P C H
`
`F A C H
`
`F A C H
`
`D S C H
`
`D S C H
`
`U S C H
`T D D o n l y
`
`U S C H
`T D D o n l y
`
`R A C H
`
`C P C H
`( F D D o n ly )
`
`D L
`T F
`T F C
`
`D o w n lin k
`T r a n s p o r t F o r m a t
`T r a n s p o r t F o r m a t C o m b in a tio n
`
`U E
`U L
`
`U s e r E q u ip m e n t
`U p li n k
`
`Figure 4.2.4.1.1: UTRAN side MAC architecture / MAC-c/sh details
`
`
`
`MAC-d entity – UTRAN Side
`4.2.4.2
`Figure 4.2.4.2.1 shows the UTRAN side MAC-d entity.
`
`The following functionality is covered:
`
`- channel switching:
`
`- dynamic transport channel type switching is performed by this entity, based on decision taken by RRC;
`
`- C/T MUX box;
`
`-
`
`the function includes the C/T field when multiplexing of several dedicated logical channels onto one
`transport channel is used.
`
`- Priority setting;
`
`- This function is responsible for priority setting on data received from DCCH / DTCH;
`
`- 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].
`
`- DL Scheduling/Priority handling;
`
`-
`
`in the downlink, scheduling and priority handling of transport channels is performed within the allowed
`transport format combinations of the TFCS assigned by the RRC.
`
`3GPP
`
`

`

`
`Release 1999
`
`- Flow Control;
`
`15
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`- a flow control function exists toward MAC-c/sh to limit buffering between MAC-d and MAC-c/sh entities.
`This function is intended to limit layer 2 signalling latency and reduce discarded and retransmitted data as a
`result of FACH or DSCH congestion. For the Iur interface this is specified in [11].
`
`A MAC-d entity using common channels is connected to a MAC-c/sh entity that handles the scheduling of the common
`channels to which the UE is assigned and DL (FACH) priority identification to MAC-c/sh;
`
`A MAC-d entity using downlink shared channel is connected to a MAC-c/sh entity that handles the shared channels to
`which the UE is assigned and indicates the level of priority of each PDU to MAC-c/sh;
`
`A MAC-d entity is responsible for mapping dedicated logical channels onto the available dedicated transport channels
`or routing the data received on a DCCH or DTCH to MAC-c/sh.
`
`One dedicated logical channel can be mapped simultaneously on DCH and DSCH. Different scheduling mechanisms
`apply for DCH and DSCH.
`
`There is one MAC-d entity in the UTRAN for each served UE.
`
`M A C - C o n tr o l
`
`D C C H
`
`D T C H
`
`D T C H
`
`U E
`
`C / T M U X
`/ P r io r ity
`s e ttin g
`
`F lo w C o n tr o l
`M A C – c / s h /
`M A C - d
`
`to M A C - c /s h
`
`C h a n n e l s w itc h i n g
`
`D e c ip h e r in g
`
`C /T
`M U X
`
`D L s c h e d u lin g /
`p r io r ity h a n d li n g
`
`M A C - d
`
`C ip h e r in g
`
`F A U S C H H a n d li n g
`
`D C H
`
`D C H
`
`F A U S C H
`
`D L
`T F
`T F C
`
`D o w n lin k
`T r a n s p o r t F o r m a t
`T r a n s p o r t F o r m a t C o m b in a tio n
`
`R N T I
`U E
`U L
`
`R a d io N e t w o r k T e m p o r a r y I d e n tity
`U s e r E q u ip m e n t
`U p li n k
`
`Figure 4.2.4.2.1: UTRAN side MAC architecture / MAC-d details
`
`
`
`Channel structure
`4.3
`The MAC operates on the channels defined below; the transport channels are described between MAC and Layer 1, the
`logical channels are described between MAC and RLC.
`
`The following subclauses provide an overview, the normative description can be found in [2] and [3] respectively.
`
`Transport channels
`4.3.1
`Common transport channel types are:
`
`3GPP
`
`

`

`
`Release 1999
`
`16
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`- Random Access Channel(s) (RACH);
`
`- Forward Access Channel(s) (FACH);
`
`- Downlink Shared Channel(s) (DSCH);
`
`- Common Packet Channel(s) (CPCH) for UL FDD operation only;
`
`- Uplink Shared Channel(s) (USCH), for TDD operation only;
`
`- Broadcast Channel (BCH);
`
`- Paging Channel (PCH).
`
`Dedicated transport channel types are:
`
`- Dedicated Channel (DCH).
`
`Logical Channels
`4.3.2
`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.
`
`Logical channel structure
`4.3.2.1
`The configuration of logical channel types is depicted in figure 4.3.2.1.
`
` Control Channel
`
`Broadcast Control Channel (BCCH)
`
`Paging Control Channel (PCCH)
`Dedicated Control Channel (DCCH)
`Common Control Channel (CCCH)
`Shared Channel Control Channel (SHCCH)
`
` Traffic Channel
`
`Dedicated Traffic Channel (DTCH)
`
`Common Traffic Channel ( CTCH)
`
`
`
`Figure 4.3.2.1: Logical channel structure
`
`Control Channels
`4.3.2.2
`Following control channels are used for transfer of control plane information only:
`
`- Broadcast Control Channel (BCCH);
`
`- Paging Control Channel (PCCH);
`
`- Common Control Channel (CCCH);
`
`- Dedicated Control Channel (DCCH);
`
`- Shared Channel Control Channel (SHCCH).
`
`Traffic Channels
`4.3.2.3
`Following traffic channels are used for the transfer of user plane information only:
`
`3GPP
`
`

`

`
`Release 1999
`
`17
`
`3GPP TS 25.321 V3.6.0 (2000-12)
`
`- Dedicated Traffic Channel (DTCH);
`
`- Common Traffic Channel (CTCH).
`
`4.3.3 Mapping between logical channels and transport channels
`The following connections between logical channels and transport channels exist:
`
`- BCCH is connected to BCH and may also be connected to FACH;
`
`- PCCH is connected to PCH;
`
`- CCCH is connected to RACH and FACH;
`
`- DCCH and DTCH can