3GPP TS 36.321 V8.3.0 (2008-09)
`
`Technical Specification
`
`3rd Generation Partnership Project;
`Technical Specification Group Radio Access Network;
`Evolved Universal Terrestrial Radio Access (E-UTRA)
`Medium Access Control (MAC) protocol specification
`(Release 8)
`
`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.
`
`Ex. 1014 - TCT Mobile (US) Inc.
`TCT Mobile (US) Inc. v. Sisvel S.P.A., IPR2021-00678
`Page 1 of 36
`
`

`

`Release 8
`
`2
`
`3GPP TS 36.321 V8.3.0 (2008-09)
`
`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.
`
`© 2008, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
`All rights reserved.
`
`3GPP
`
`Ex. 1014 - TCT Mobile (US) Inc.
`TCT Mobile (US) Inc. v. Sisvel S.P.A., IPR2021-00678
`Page 2 of 36
`
`

`

`Release 8
`
`3
`
`3GPP TS 36.321 V8.3.0 (2008-09)
`
`Contents
`
`Foreword............................................................................................................................................................. 5
`
`1
`
`2
`
`3
`3.1
`3.2
`
`Scope ........................................................................................................................................................ 6
`
`References ................................................................................................................................................ 6
`
`Definitions and abbreviations ................................................................................................................... 6
`Definitions ......................................................................................................................................................... 6
`Abbreviations ..................................................................................................................................................... 7
`
`4
`4.1
`4.2
`4.2.1
`4.3
`4.3.1
`4.3.2
`4.4
`4.5
`4.5.1
`4.5.2
`4.5.3
`4.5.3.1
`4.5.3.2
`
`General ..................................................................................................................................................... 8
`Introduction........................................................................................................................................................ 8
`MAC architecture .............................................................................................................................................. 8
`MAC Entities ............................................................................................................................................... 8
`Services .............................................................................................................................................................. 8
`Services provided to upper layers ................................................................................................................ 8
`Services expected from physical layer ......................................................................................................... 8
`Functions ........................................................................................................................................................... 9
`Channel structure ............................................................................................................................................... 9
`Transport Channels ...................................................................................................................................... 9
`Logical Channels ........................................................................................................................................ 10
`Mapping of Transport Channels to Logical Channels ................................................................................ 10
`Uplink mapping .................................................................................................................................... 10
`Downlink mapping ............................................................................................................................... 11
`
`5
`5.1
`5.1.1
`5.1.2
`5.1.3
`5.1.4
`5.1.5
`5.1.6
`5.2
`5.3
`5.3.1
`5.3.2
`5.3.2.1
`5.3.2.2
`5.3.3
`5.4
`5.4.1
`5.4.2
`5.4.2.1
`5.4.2.2
`5.4.3
`5.4.3.1
`5.4.3.2
`5.4.4
`5.4.5
`5.4.6
`5.5
`5.6
`5.7
`5.8
`5.9
`5.X
`
`MAC procedures .................................................................................................................................... 11
`Random Access procedure ............................................................................................................................... 11
`Random Access Procedure initialization .................................................................................................... 11
`Random Access Resource selection ........................................................................................................... 12
`Random Access Preamble transmission ..................................................................................................... 13
`Random Access Response reception .......................................................................................................... 13
`Contention Resolution ................................................................................................................................ 14
`Completion of the Random Access procedure ........................................................................................... 15
`Maintenance of Uplink Time Alignment ......................................................................................................... 16
`DL-SCH data transfer ...................................................................................................................................... 16
`DL Assignment reception ........................................................................................................................... 16
`HARQ operation ........................................................................................................................................ 17
`HARQ Entity ........................................................................................................................................ 17
`HARQ process ...................................................................................................................................... 18
`Disassembly and demultiplexing ................................................................................................................ 19
`UL-SCH data transfer ...................................................................................................................................... 19
`UL Grant reception .................................................................................................................................... 19
`HARQ operation ........................................................................................................................................ 20
`HARQ entity ......................................................................................................................................... 20
`HARQ process ...................................................................................................................................... 21
`Multiplexing and assembly ........................................................................................................................ 22
`Logical channel prioritization ............................................................................................................... 22
`Multiplexing of MAC SDUs ................................................................................................................ 23
`Scheduling Request .................................................................................................................................... 23
`Buffer Status Reporting .............................................................................................................................. 23
`Power Headroom Reporting ....................................................................................................................... 24
`PCH reception .................................................................................................................................................. 25
`BCH reception ................................................................................................................................................. 25
`Discontinuous Reception (DRX) ..................................................................................................................... 25
`MAC reconfiguration ....................................................................................................................................... 26
`MAC Reset ...................................................................................................................................................... 26
`Handling of unknown, unforeseen and erroneous protocol data ...................................................................... 26
`
`3GPP
`
`Ex. 1014 - TCT Mobile (US) Inc.
`TCT Mobile (US) Inc. v. Sisvel S.P.A., IPR2021-00678
`Page 3 of 36
`
`

`

`Release 8
`
`4
`
`3GPP TS 36.321 V8.3.0 (2008-09)
`
`6
`6.1
`6.1.1
`6.1.2
`6.1.3
`6.1.3.1
`6.1.3.2
`6.1.3.3
`6.1.3.4
`6.1.3.5
`6.1.3.6
`6.1.4
`6.1.5
`6.2
`6.2.1
`6.2.2
`6.2.3
`
`Protocol Data Units, formats and parameters ......................................................................................... 27
`Protocol Data Units .......................................................................................................................................... 27
`General ....................................................................................................................................................... 27
`MAC PDU (DL-SCH and UL-SCH) .......................................................................................................... 27
`MAC Control Elements .............................................................................................................................. 28
`Buffer Status Report MAC Control Elements ...................................................................................... 28
`C-RNTI MAC Control Element ........................................................................................................... 29
`DRX Command MAC Control Element ............................................................................................... 30
`UE Contention Resolution Identity MAC Control Element ................................................................. 30
`Timing Advance MAC Control Element .............................................................................................. 30
`Power Headroom MAC Control Element ............................................................................................. 31
`MAC PDU (transparent MAC) .................................................................................................................. 31
`MAC PDU (Random Access Response) .................................................................................................... 31
`Formats and parameters ................................................................................................................................... 32
`MAC header for DL-SCH and UL-SCH .................................................................................................... 32
`MAC header for Random Access Response .............................................................................................. 33
`MAC payload for Random Access Response ............................................................................................ 33
`
`7
`7.1
`7.2
`
`Variables and constants .......................................................................................................................... 34
`RNTI values ..................................................................................................................................................... 34
`Backoff Parameter values ................................................................................................................................ 34
`
`Annex A (informative):
`
`Change history ............................................................................................... 35
`
`3GPP
`
`Ex. 1014 - TCT Mobile (US) Inc.
`TCT Mobile (US) Inc. v. Sisvel S.P.A., IPR2021-00678
`Page 4 of 36
`
`

`

`Release 8
`
`5
`
`3GPP TS 36.321 V8.3.0 (2008-09)
`
`Foreword
`
`This Technical Specification 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
`
`Ex. 1014 - TCT Mobile (US) Inc.
`TCT Mobile (US) Inc. v. Sisvel S.P.A., IPR2021-00678
`Page 5 of 36
`
`

`

`Release 8
`
`6
`
`3GPP TS 36.321 V8.3.0 (2008-09)
`
`1 Scope
`
`The present document specifies the E-UTRA MAC protocol.
`
`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 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]
`
`[6]
`
`[7]
`
`[8]
`
`3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
`
`3GPP TR 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Layer
`Procedures".
`
`3GPP TS 36.322: “Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control
`(RLC) protocol specification”.
`
`3GPP TS 36.323: “Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data
`Convergence Protocol (PDCP) Specification”.
`
`3GPP TS 36.212: “Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and
`channel coding”.
`
`3GPP TS 36.214: “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer;
`Measurements”.
`
`3GPP TS 36.211: “Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels
`and Modulation”.
`
`3GPP TS 36.331: “Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource
`Control (RRC); Protocol specification”.
`
`3
`
`Definitions and abbreviations
`
`3.1
`
`Definitions
`
`For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A
`term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
`
`Active Time: time during which the UE monitors the PDCCH for a PDCCH-subframe. Section 5.7 defines the
`conditions for which a subframe is included as part of Active Time.
`
`Contention Resolution Timer: Specifies the number of consecutive PDCCH-subframe(s) during which the UE shall
`monitor the PDCCH after the uplink message containing the C-RNTI MAC control element or the uplink message
`associated with UE Contention Resolution Identity submitted from higher layer is transmitted.
`
`DRX Cycle: Specifies the periodic repetition of the On Duration followed by a possible period of inactivity (see figure
`3.1-1 below).
`
`3GPP
`
`Ex. 1014 - TCT Mobile (US) Inc.
`TCT Mobile (US) Inc. v. Sisvel S.P.A., IPR2021-00678
`Page 6 of 36
`
`

`

`Release 8
`
`7
`
`3GPP TS 36.321 V8.3.0 (2008-09)
`
`Figure 3.1-1: DRX Cycle
`
`DRX Inactivity Timer: Specifies the number of consecutive PDCCH-subframe(s) after successfully decoding a
`PDCCH indicating an initial UL or DL user data transmission for this UE.
`
`DRX Retransmission Timer: Specifies the maximum number of consecutive PDCCH-subframe(s) for as soon as a DL
`retransmission is expected by the UE.
`
`DRX Short Cycle Timer: This parameter specifies the number of consecutive subframe(s)the UE shall follow the short
`DRX cycle after the DRX Inactivity Timer has expired.
`
`HARQ information: HARQ information consists of New Data Indicator (NDI), Redundancy Version (RV), Transport
`Block (TB) size. For DL-SCH transmissions the HARQ info also includes HARQ process ID.
`
`HARQ RTT Timer: This parameter specifies the minimum amount of subframe(s) before a DL HARQ retransmission
`is expected by the UE.
`
`On Duration Timer: Specifies the number of consecutive PDCCH-subframe(s) at the beginning of a DRX Cycle.
`
`RA-RNTI: The Random Access RNTI is used on the PDCCH when Random Access Response messages are
`transmitted. It unambiguously identifies which time-frequency resource was utilized by the UE to transmit the Random
`Access preamble.
`
`PDCCH-subframe: For FDD UE operation, this represents any subframe; for TDD, only downlink subframes.
`
`NOTE: A timer is running once it is started, until it is stopped or until it expires.
`
`NOTE: When defining On Duration Timer, DRX Inactivity Timer, DRX Retransmission Timer and Contention
`Resolution Timer, PDCCH-subframes and subframes including DwPTS are considered as subframes
`where the timer, if running, shall be updated.
`
`3.2
`
`Abbreviations
`
`For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An
`abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
`TR 21.905 [1].
`
`BSR
`C-RNTI
`CQI
`E-UTRA
`E-UTRAN
`MAC
`LCG
`PHR
`PMI
`P-RNTI
`RA-RNTI
`RI
`RNTI
`SI-RNTI
`SR
`SRS
`
` Buffer Status Report
` Cell RNTI
` Channel Quality Indicator
` Evolved UMTS Terrestrial Radio Access
` Evolved UMTS Terrestrial Radio Access Network
` Medium Access Control
` Logical Channel Group
`
`Power Headroom Report
`
`Precoding Matrix Index
`
`Paging RNTI
` Random Access RNTI
` Rank Indicator
` Radio Network Temporary Identifier
`
`System Information RNTI
`
`Scheduling Request
`
`Sounding Reference Symbols
`
`3GPP
`
`Ex. 1014 - TCT Mobile (US) Inc.
`TCT Mobile (US) Inc. v. Sisvel S.P.A., IPR2021-00678
`Page 7 of 36
`
`

`

`Release 8
`
`8
`
`3GPP TS 36.321 V8.3.0 (2008-09)
`
` Transport Block
`TB
`TPC-PUCCH-RNTI Transmit Power Control-Physical Uplink Control Channel-RNTI
`TPC-PUSCH-RNTI Transmit Power Control-Physical Uplink Shared Channel-RNTI
`
`4
`
`General
`
`4.1
`
`Introduction
`
`The objective is to describe the MAC architecture and the MAC entity from a functional point of view.
`
`4.2
`
`MAC architecture
`
`The description in this sub clause is a model and does not specify or restrict implementations.
`
`RRC is in control of configuration of MAC.
`
`4.2.1 MAC Entities
`
`E-UTRA defines two MAC entities; one in the UE and one in the E-UTRAN. These MAC entities handle the following
`transport channels:
`
`- Broadcast Channel (BCH);
`
`- Downlink Shared Channel (DL-SCH);
`
`- Paging Channel (PCH);
`
`- Uplink Shared Channel (UL-SCH);
`
`- Random Access Channel(s) (RACH).
`
`The exact functions performed by the MAC entities are different in the UE from those performed in the E-UTRAN.
`
`4.3
`
`Services
`
`4.3.1
`
`Services provided to upper layers
`
`This clause describes the different services provided by MAC sublayer to upper layers.
`
`- data transfer
`
`-
`
`radio resource allocation
`
`4.3.2
`
`Services expected from physical layer
`
`The physical layer provides the following services to MAC:
`
`- data transfer services;
`
`-
`
`-
`
`signalling of HARQ feedback;
`
`signalling of Scheduling Request;
`
`- measurements (e.g. Channel Quality Indication (CQI)).
`
`The access to the data transfer services is through the use of transport channels. The characteristics of a transport
`channel are defined by its transport format (or format set), specifying the physical layer processing to be applied to the
`
`3GPP
`
`Ex. 1014 - TCT Mobile (US) Inc.
`TCT Mobile (US) Inc. v. Sisvel S.P.A., IPR2021-00678
`Page 8 of 36
`
`

`

`Release 8
`
`9
`
`3GPP TS 36.321 V8.3.0 (2008-09)
`
`transport channel in question, such as channel coding and interleaving, and any service-specific rate matching as
`needed.
`
`4.4
`
`Functions
`
`The following functions are supported by MAC sublayer:
`
`- mapping between logical channels and transport channels;
`
`- multiplexing of MAC SDUs from one or different logical channels onto transport blocks (TB) to be delivered to
`the physical layer on transport channels;
`
`- demultiplexing of MAC SDUs from one or different logical channels from transport blocks (TB) delivered from
`the physical layer on transport channels;
`
`-
`
`scheduling information reporting;
`
`- error correction through HARQ;
`
`- priority handling between UEs by means of dynamic scheduling;
`
`- priority handling between logical channels of one UE;
`
`- Logical Channel prioritisation;
`
`-
`
`transport format selection.
`
`NOTE: How the multiplexing relates to the QoS of the multiplexed logical channels is FFS.
`
`The location of the different functions and their relevance for uplink and downlink respectively is illustrated in Table
`4.4-1.
`
`Table 4.4-1: MAC function location and link direction association.
`
`MAC function
`Mapping between logical channels and transport channels
`
`UE
`X
`
`eNB
`
`Multiplexing
`
`Demultiplexing
`
`Error correction through HARQ
`
`Transport Format Selection
`Priority handling between UEs
`Priority handling between logical channels of one UE
`Logical Channel prioritisation
`Scheduling information reporting
`
`X
`
`X
`
`X
`
`X
`X
`X
`X
`
`X
`
`X
`
`X
`
`X
`X
`
`Downlink
`X
`X
`
`Uplink
`X
`X
`X
`
`X
`X
`
`X
`X
`X
`X
`X
`
`X
`X
`X
`X
`X
`X
`X
`X
`
`4.5
`
`Channel structure
`
`The MAC sublayer operates on the channels defined below; transport channels are SAPs between MAC and Layer 1,
`logical channels are SAPs between MAC and RLC.
`
`4.5.1
`
`Transport Channels
`
`The transport channels used by MAC are described in Table 4.5.1-1 below.
`
`3GPP
`
`Ex. 1014 - TCT Mobile (US) Inc.
`TCT Mobile (US) Inc. v. Sisvel S.P.A., IPR2021-00678
`Page 9 of 36
`
`

`

`Release 8
`
`10
`
`3GPP TS 36.321 V8.3.0 (2008-09)
`
`Table 4.5.1-1: Transport channels used by MAC
`
`Transport channel name
`Broadcast Channel
`Downlink Shared Channel
`Paging Channel
`Uplink Shared Channel
`Random Access Channel
`
`Acronym
`BCH
`DL-SCH
`PCH
`UL-SCH
`RACH
`
`Downlink
`X
`X
`X
`
`Uplink
`
`X
`X
`
`4.5.2
`
`Logical Channels
`
`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.
`
`MAC provides the control and traffic channels listed in Table 4.5.2-1 below. When MAC uses the PDCCH to indicate
`radio resource allocation, the RNTI that is mapped on the PDCCH depends on the logical channel type:
`
`- C-RNTI, Temporary C-RNTI and Semi-Persistent Scheduling C-RNTI for DCCH and DTCH;
`
`- P-RNTI for PCCH;
`
`- RA-RNTI for Random Access Response on DL-SCH;
`
`- Temporary C-RNTI for CCCH during the random access procedure;
`
`- SI-RNTI for BCCH.
`
`Table 4.5.2-1: Logical channels provided by MAC.
`
`Logical channel name
`Broadcast Control Channel
`Paging Control Channel
`Common Control Channel
`Dedicated Control Channel
`Dedicated Traffic Channel
`
`Acronym
`BCCH
`PCCH
`CCCH
`DCCH
`DTCH
`
`Control channel
`X
`X
`X
`X
`
`Traffic channel
`
`X
`
`4.5.3 Mapping of Transport Channels to Logical Channels
`
`The mapping of logical channels on transport channels depends on the multiplexing that is configured by RRC.
`
`4.5.3.1
`
`Uplink mapping
`
`The MAC entity is responsible for mapping logical channels for the uplink onto uplink transport channels. The uplink
`logical channels can be mapped as described in Figure 4.5.3.1-1 and Table 4.5.3.1-1.
`
`CCCH
`
`DCCH
`
`DTCH
`
`Uplink
`Logical channels
`
`RACH
`
`UL-SCH
`
`Uplink
`Transport channels
`
`Figure 4.5.3.1-1
`
`3GPP
`
`Ex. 1014 - TCT Mobile (US) Inc.
`TCT Mobile (US) Inc. v. Sisvel S.P.A., IPR2021-00678
`Page 10 of 36
`
`

`

`Release 8
`
`11
`
`3GPP TS 36.321 V8.3.0 (2008-09)
`
`Table 4.5.3.1-1: Uplink channel mapping.
`
`Transport channel
`Logical channel
`CCCH
`DCCH
`DTCH
`
`UL-SCH
`
`RACH
`
`X
`X
`X
`
`4.5.3.2
`
`Downlink mapping
`
`The MAC entity is responsible for mapping the downlink logical channels to downlink transport channels. The
`downlink logical channels can be mapped as described in Figure 4.5.3.2-1 and Table 4.5.3.2-1.
`
`Figure 4.5.3.2-1
`
`Table 4.5.3.2-1: Downlink channel mapping.
`
`Transport channel
`Logical channel
`BCCH
`PCCH
`CCCH
`DCCH
`DTCH
`
`BCH
`
`PCH
`
`DL-SCH
`
`X
`
`X
`
`X
`
`X
`X
`X
`
`5
`
`MAC procedures
`
`5.1
`
`Random Access procedure
`
`5.1.1
`
`Random Access Procedure initialization
`
`The Random Access procedure described in this subclause is initiated by a PDCCH order or by the MAC sublayer
`itself. The PDCCH order or RRC optionally indicate a Random Access Preamble and PRACH resource.
`
`Before the procedure can be initiated, the following information is assumed to be available:
`
`-
`
`the available set of PRACH resources for the transmission of the Random Access Preamble and their
`corresponding RA-RNTIs.
`
`-
`
`the groups of Random Access Preambles and the set of available Random Access Preambles in each group:
`
`The preambles that are contained in Random Access Preambles group A and Random Access Preambles group B
`are calculated from the parameters numberOfRA-Preambles and sizeOfRA-PreamblesGroupA [8]:
`
`3GPP
`
`Ex. 1014 - TCT Mobile (US) Inc.
`TCT Mobile (US) Inc. v. Sisvel S.P.A., IPR2021-00678
`Page 11 of 36
`
`

`

`Release 8
`
`12
`
`3GPP TS 36.321 V8.3.0 (2008-09)
`
`If sizeOfRA-PreamblesGroupA is equal to numberOfRA-Preambles then there is no Random Access Preambles
`group B. The preambles in Random Access Preamble group A are the preambles 1 to sizeOfRA-
`PreamblesGroupA and, if it exists, the preambles in Random Access Preamble group B are the preambles
`sizeOfRA-PreamblesGroupA +1 to numberOfRA-Preambles from the set of 64 preambles as defined in [7].
`
`the thresholds, PARTITION_PATHLOSS_THRESHOLD and MESSAGE_SIZE_GROUP_A, that are required
`for selecting one of the two groups of Random Access Preambles.
`
`the RA response window size ra-ResponseWindowSize [8].
`
`the power-ramping factor POWER_RAMP_STEP.
`
`the parameter PREAMBLE_TRANS_MAX [integer > 0].
`
`the initial preamble power PREAMBLE_ INITIAL_RECEIVED_TARGET_POWER.
`
`the parameter Maximum number of Message3 HARQ transmissions.
`
`-
`
`-
`
`-
`
`-
`
`-
`
`-
`
`[Note that the above parameters may be updated from higher layers before each Random Access procedure is initiated.]
`
`The Random Access procedure shall be performed as follows:
`
`- Flush the [Message3] buffer;
`
`-
`
`-
`
`set the PREAMBLE_TRANSMISSION_COUNTER to 1;
`
`set the backoff parameter value in the UE to 0 ms;
`
`- proceed to the selection of the Random Access Resource (see subclause 5.1.2).
`
`NOTE: There is only one Random Access procedure ongoing at any point in time. If the UE receives a request for
`a new Random Access procedure while another is already ongoing, it is up to UE implementation whether
`to continue with the ongoing procedure or start with the new procedure.
`
`5.1.2
`
`Random Access Resource selection
`
`The Random Access Resource procedure shall be performed as follows:
`
`-
`
`If the Random Access Preamble and PRACH resource have been explicitly signalled:
`
`-
`
`the UE can directly proceed to the transmission of the Random Access Preamble (see subclause 5.1.3).
`
`- else the Random Access Preamble shall be selected by the UE as follows:
`
`-
`
`If the uplink message containing the C-RNTI MAC control element or the uplink message including the
`CCCH SDU has not yet been transmitted, the UE shall:
`
`-
`
`if Random Access Preambles group B exists and if the potential message size (data available for
`transmission plus MAC header and, where required, MAC control elements) is greater than
`MESSAGE_SIZE_GROUP_A and if the pathloss is less than PARTITION_PATHLOSS_THRESHOLD
`then:
`
`-
`
`select the Random Access Preambles group B;
`
`- else:
`
`-
`
`select the Random Access Preambles group A.
`
`- else, if the uplink message containing the C-RNTI MAC control element or the uplink message including the
`CCCH SDU is being retransmitted, the UE shall:
`
`-
`
`select the same group of Random Access Preambles as was used for the preamble transmission attempt
`corresponding to the first transmission of the uplink message containing the C-RNTI MAC control
`element or the uplink message including the CCCH SDU.
`
`3GPP
`
`Ex. 1014 - TCT Mobile (US) Inc.
`TCT Mobile (US) Inc. v. Sisvel S.P.A., IPR2021-00678
`Page 12 of 36
`
`

`

`Release 8
`
`13
`
`3GPP TS 36.321 V8.3.0 (2008-09)
`
`-
`
`-
`
`randomly select a Random Access Preamble within the selected group. The random function shall be such
`that each of the allowed selections can be chosen with equal probability;
`
`if more than one PRACH resources are available in the same subframe (TDD), randomly select one. The
`random function shall be such that each of the allowed selections can be chosen with equal probability;
`
`- proceed to the transmission of the Random Access Preamble (see subclause 5.1.3).
`
`5.1.3
`
`Random Access Preamble transmission
`
`The random-access procedure shall be performed as follows:
`
`-
`
`If PREAMBLE_TRANSMISSION_COUNTER = PREAMBLE_TRANS_MAX + 1:
`
`-
`
`indicate a Random Access problem to upper layers.
`
`[- set the parameter PREAMBLE_RECEIVED_TARGET_POWER to
`PREAMBLE_INITIAL_RECEIVED_TARGET_POWER + (PREAMBLE_TRANSMISSION_COUNTER-1) *
`POWER_RAMP_STEP;]
`
`- determine the next available Random Access occasion (a UE may take into account the possible occurrence of
`measurement gaps when determining the next available Random Access occasion);
`
`-
`
`instruct the physical layer to transmit a preamble using the selected PRACH resource, corresponding RA-RNTI,
`preamble index and PREAMBLE_RECEIVED_TARGET_POWER.
`
`5.1.4
`
`Random Access Response reception
`
`Once the Random Access Preamble is transmitted and regardless of the possible occurrence of a measurement gap, the
`UE shall monitor the PDCCH for Random Access Response(s) identified by the RA-RNTI defined below, in the TTI
`window RA_WINDOW_BEGIN—RA_WINDOW_END which starts at the subframe that contains the end of the
`preamble transmission [7] plus three subframes and has length ra-ResponseWindowSize subframes. The RA-RNTI
`associated with the PRACH resource in which the Random Access Preamble is transmitted, is computed as:
`
`RA-RNTI= t_id+10*f_id
`
`2;8B8 D3<7 <C D;8 <>78G ?9 D;8 9<BCD CE59B4=8 ?9 D;8 C@86<9<87 ./*+- B8C?EB68 "&I D3<7 )’&#$ 4>7 93<7 <C D;8 <>78G ?9 D;8
`C@86<9<87 ./*+- B8C?EB68 F<D;<> D;4D CE59B4=8$ <> 4C68>7<>: ?B78B ?9 9B8AE8>6H 7?=4<> "&I 93<7) (#% 0;8 1, =4H
`stop monitoring for Random Access Response(s) after successful reception of a Random Access Response
`corresponding to the Random Access Preamble transmission.
`
`-
`
`If a downlink assignment for this TTI has been received on the PDCCH for the RA-RNTI and the received TB is
`successfully decoded, the UE shall regardless of the possible occurrence of a measurement gap:
`
`-
`
`if the Random Access Response contains a Backoff Indicator subheader:
`
`-
`
`set the backoff parameter value in the UE as indicated by the BI field of the Backoff Indicator subheader
`and Table 7.2-1.
`
`- else, set the backoff parameter value in the UE to 0 ms.
`
`-
`
`if the Random Access Response contains a Random Access Preamble identifier corresponding to the
`transmitted Rando