ETSI TS 125 224 V3.12.0 (2002-12)
`
`Technical Specification
`
`Universal Mobile Telecommunications System (UMTS);
`Physical layer procedures (TDD)
`(3GPP TS 25.224 version 3.12.0 Release 1999)
`
`Hewlett Packard Enterprise Co. Ex. 1008, Page 1 of 23
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01376
`
`

`

`
`3GPP TS 25.224 version 3.12.0 Release 1999
`
`1
`
`ETSI TS 125 224 V3.12.0 (2002-12)
`
`
`
`
`
`
`
`Reference
`RTS/TSGR-0125224v3c0
`
`Keywords
`UMTS
`
`ETSI
`
`650 Route des Lucioles
`F-06921 Sophia Antipolis Cedex - FRANCE
`
`Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
`
`Siret N° 348 623 562 00017 - NAF 742 C
`Association à but non lucratif enregistrée à la
`Sous-Préfecture de Grasse (06) N° 7803/88
`
`
`Important notice
`
`Individual copies of the present document can be downloaded from:
`http://www.etsi.org
`
`The present document may be made available in more than one electronic version or in print. In any case of existing or
`perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
`In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
`within ETSI Secretariat.
`
`Users of the present document should be aware that the document may be subject to revision or change of status.
`Information on the current status of this and other ETSI documents is available at
`http://portal.etsi.org/tb/status/status.asp
`
`If you find errors in the present document, send your comment to:
`editor@etsi.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.
`
`© European Telecommunications Standards Institute 2002.
`All rights reserved.
`
`DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members.
`TIPHONTM and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
`3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
`
`ETSI
`
`Hewlett Packard Enterprise Co. Ex. 1008, Page 2 of 23
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01376
`
`

`

`
`3GPP TS 25.224 version 3.12.0 Release 1999
`
`2
`
`ETSI TS 125 224 V3.12.0 (2002-12)
`
`Intellectual Property Rights
`IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
`pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
`in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
`respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
`server (http://webapp.etsi.org/IPR/home.asp).
`
`All published ETSI deliverables shall include information which directs the reader to the above source of information.
`
`Foreword
`This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
`
`The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
`GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
`
`The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
`http://webapp.etsi.org/key/queryform.asp .
`
`ETSI
`
`Hewlett Packard Enterprise Co. Ex. 1008, Page 3 of 23
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01376
`
`

`

`
`3GPP TS 25.224 version 3.12.0 Release 1999
`
`3
`
`ETSI TS 125 224 V3.12.0 (2002-12)
`
`Contents
`
`2
`
`3
`
`Intellectual Property Rights ................................................................................................................................2
`Foreword.............................................................................................................................................................2
`Foreword.............................................................................................................................................................5
`Scope ........................................................................................................................................................6
`1
`References ................................................................................................................................................6
`Abbreviations ...........................................................................................................................................7
`Physical layer procedures (TDD) .............................................................................................................8
`General ...............................................................................................................................................................8
`Transmitter Power Control .................................................................................................................................8
`General Parameters .......................................................................................................................................8
`Uplink Control ..............................................................................................................................................8
`General Limits.........................................................................................................................................8
`PRACH ...................................................................................................................................................8
`DPCH, PUSCH .......................................................................................................................................8
`Gain Factors ......................................................................................................................................8
`Out of synchronisation handling......................................................................................................10
`Downlink Control .......................................................................................................................................10
`P-CCPCH ..............................................................................................................................................10
`S-CCPCH, PICH...................................................................................................................................10
`SCH.......................................................................................................................................................10
`DPCH, PDSCH .....................................................................................................................................10
`Out of synchronisation handling......................................................................................................11
`Timing Advance ...............................................................................................................................................11
`Synchronisation procedures..............................................................................................................................11
`Cell Search..................................................................................................................................................11
`Dedicated channel synchronisation.............................................................................................................12
`Synchronisation primitives....................................................................................................................12
`General ............................................................................................................................................12
`Downlink synchronisation primitives..............................................................................................12
`Uplink synchronisation primitives...................................................................................................13
`Radio link monitoring ...........................................................................................................................13
`Downlink radio link failure .............................................................................................................13
`Uplink radio link failure/restore ......................................................................................................13
`Discontinuous transmission (DTX) of Radio Frames.......................................................................................13
`Use of Special Bursts for DTX ...................................................................................................................13
`Use of Special Bursts for Initial Establishment / Reconfiguration .............................................................14
`Downlink Transmit Diversity...........................................................................................................................14
`Transmit Diversity for PDSCH and DPCH ................................................................................................14
`Transmit Diversity for SCH........................................................................................................................14
`SCH Transmission Scheme...................................................................................................................15
`Transmit Diversity for Beacon Channels....................................................................................................15
`SCTD Transmission Scheme ................................................................................................................15
`Random access procedure ................................................................................................................................16
`Physical random access procedure..............................................................................................................16
`DSCH procedure ..............................................................................................................................................17
`DSCH procedure with TFCI indication ......................................................................................................17
`DSCH procedure with midamble indication...............................................................................................17
`
`4
`4.1
`4.2
`4.2.1
`4.2.2
`4.2.2.1
`4.2.2.2
`4.2.2.3
`4.2.2.3.1
`4.2.2.3.2
`4.2.3
`4.2.3.1
`4.2.3.2
`4.2.3.3
`4.2.3.4
`4.2.3.4.1
`4.3
`4.4
`4.4.1
`4.4.2
`4.4.2.1
`4.4.2.1.1
`4.4.2.1.2
`4.4.2.1.3
`4.4.2.2
`4.4.2.2.1
`4.4.2.2.2
`4.5
`4.5.1
`4.5.2
`4.6
`4.6.1
`4.6.2
`4.6.2.1
`4.6.3
`4.6.3.1
`4.7
`4.7.1
`4.8
`4.8.1
`4.8.2
`
`Annex A (informative): Power Control ........................................................................................................18
`A.1 Example Implementation of Downlink Power Control in the UE..........................................................18
`
`Annex B (informative): Determination of Weight Information .................................................................19
`
`ETSI
`
`Hewlett Packard Enterprise Co. Ex. 1008, Page 4 of 23
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01376
`
`

`

`
`3GPP TS 25.224 version 3.12.0 Release 1999
`
`4
`
`ETSI TS 125 224 V3.12.0 (2002-12)
`
`B.1 STD Weights..........................................................................................................................................19
`B.2 TxAA Weights .......................................................................................................................................19
`
`Annex C (informative): Cell search procedure............................................................................................20
`
`Annex D (informative): Change history .......................................................................................................21
`History ..............................................................................................................................................................23
`
`
`ETSI
`
`Hewlett Packard Enterprise Co. Ex. 1008, Page 5 of 23
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01376
`
`

`

`
`3GPP TS 25.224 version 3.12.0 Release 1999
`
`5
`
`ETSI TS 125 224 V3.12.0 (2002-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.
`
`ETSI
`
`Hewlett Packard Enterprise Co. Ex. 1008, Page 6 of 23
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01376
`
`

`

`
`3GPP TS 25.224 version 3.12.0 Release 1999
`
`6
`
`ETSI TS 125 224 V3.12.0 (2002-12)
`
`Scope
`1
`The present document describes the Physical Layer Procedures in the TDD mode of UTRA.
`
`References
`2
`The following documents contain provisions which, through reference in this text, constitute provisions of the present
`document.
`• References are either specific (identified by date of publication, edition number, version number, etc.) or
`non-specific.
`• For a specific reference, subsequent revisions do not apply.
`• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
`a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
`Release as the present document.
`
`[1]
`
`[2]
`
`[3]
`
`[4]
`
`[5]
`
`[6]
`
`[7]
`
`[8]
`
`[9]
`
`[10]
`
`[11]
`
`[12]
`
`[13]
`
`[14]
`
`[15]
`
`[16]
`
`[17]
`
`[18]
`
`[19]
`
`3GPP TS 25.201: "Physical layer - general description".
`
`3GPP TS 25.102: "UE physical layer capabilities".
`
`3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels
`(FDD)".
`
`3GPP TS 25.212: "Multiplexing and channel coding (FDD)".
`
`3GPP TS 25.213: "Spreading and modulation (FDD)".
`
`3GPP TS 25.214: "Physical layer procedures (FDD)".
`
`3GPP TS 25.215: "Physical Layer - Measurements (FDD)".
`
`3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels
`(TDD)".
`
`3GPP TS 25.222: "Multiplexing and channel coding (TDD)".
`
`3GPP TS 25.223: "Spreading and modulation (TDD)".
`
`3GPP TS 25.225: "Physical Layer - Measurements (TDD)".
`
`3GPP TS 25.301: "Radio Interface Protocol Architecture".
`
`3GPP TS 25.302: "Services Provided by the Physical Layer".
`
`3GPP TS 25.401: "UTRAN Overall Description".
`
`3GPP TS 25.331: "RRC Protocol Specification"
`
`3GPP TS 25.433: " UTRAN Iub Interface NBAP Signalling"
`
`3GPP TS 25.105: " UTRA (BS) TDD; Radio transmission and Reception"
`
`3GPP TS 25.321: " MAC protocol specification"
`
`3GPP TS 25.303: " Interlayer Procedures in Connected Mode"
`
`ETSI
`
`Hewlett Packard Enterprise Co. Ex. 1008, Page 7 of 23
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01376
`
`

`

`
`3GPP TS 25.224 version 3.12.0 Release 1999
`
`7
`
`ETSI TS 125 224 V3.12.0 (2002-12)
`
`Abbreviations
`3
`For the purposes of the present document, the following abbreviations apply:
`
`ASC
`BCCH
`BCH
`CCTrCH
`CDMA
`CRC
`DCA
`DL
`DPCH
`DTX
`FACH
`FDD
`ISCP
`MAC
`NRT
`P-CCPCH
`PC
`PDSCH
`PRACH
`PUSCH
`RACH
`RL
`RRC
`RSCP
`RT
`RU
`SBGP
`SBP
`SBSP
`S-CCPCH
`SCH
`SCTD
`SFN
`SIR
`SSCH
`STD
`TA
`TDD
`TF
`TFC
`TFCI
`TFCS
`TPC
`TSTD
`TTI
`TxAA
`UE
`UL
`UMTS
`UTRAN
`VBR
`
`Access Service Class
`Broadcast Control Channel
`Broadcast Channel
`Coded Composite Transport Channel
`Code Division Multiple Access
`Cyclic Redundancy Check
`Dynamic Channel Allocation
`Downlink
`Dedicated Physical Channel
`Discontinuous Transmission
`Forward Access Channel
`Frequency Division Duplex
`Interference Signal Code Power
`Medium Access Control
`Non-Real Time
`Primary Common Control Physical Channel
`Power Control
`Physical Downlink Shared Channel
`Physical Random Access Channel
`Physical Uplink Shared Channel
`Random Access Channel
`Radio Link
`Radio Resource Control
`Received Signal Code Power
`Real Time
`Resource Unit
`Special Burst Generation Gap
`Special Burst Period
`Special Burst Scheduling Period
`Secondary Common Control Physical Channel
`Synchronisation Channel
`Space Code Transmit Diversity
`System Frame Number
`Signal–to-Interference Ratio
`Secondary Synchronisation Channel
`Selective Transmit Diversity
`Timing Advance
`Time Division Duplex
`Transport Format
`Transport Format Combination
`Transport Format Combination Indicator
`Transport Format Combination Set
`Transmit Power Control
`Time Switched Transmit Diversity
`Transmission Time Interval
`Transmit Adaptive Antennas
`User Equipment
`Uplink
`Universal Mobile Telecommunications System
`UMTS Radio Access Network
`Variable Bit Rate
`
`ETSI
`
`Hewlett Packard Enterprise Co. Ex. 1008, Page 8 of 23
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01376
`
`

`

`
`3GPP TS 25.224 version 3.12.0 Release 1999
`
`8
`
`ETSI TS 125 224 V3.12.0 (2002-12)
`
`4
`
`4.1
`
`4.2
`
`Physical layer procedures (TDD)
`
`General
`
`Transmitter Power Control
`
`4.2.1 General Parameters
`
`Power control is applied for the TDD mode to limit the interference level within the system thus reducing the intercell
`interference level and to reduce the power consumption in the UE.
`
`All codes within one timeslot allocated to the same CCTrCH use the same transmission power, in case they have the
`same spreading factor.
`
`Table 1: Transmit Power Control characteristics
`
`
`Power control rate
`
`TPC Step size
`Remarks
`
`Uplink
`
`Variable
`1-7 slots delay (2 slot SCH)
`1-14 slots delay (1 slot SCH)
`--
`All figures are without processing and
`measurement times
`
`Downlink
`Variable, with rate depending on
`the slot allocation.
`
`1dB or 2 dB or 3 dB
`
`
`
`
`4.2.2
`
`Uplink Control
`
`4.2.2.1
`
`General Limits
`
`During the operation of the uplink power control procedure the UE transmit power shall not exceed a maximum
`allowed value which is the lower out of the maximum output power of the terminal power class and a value which may
`be set by higher layer signalling.
`
`Uplink power control shall be performed while the total UE transmit power is below the maximum allowed output
`power. In some cases the total UE transmit power in a timeslot after uplink power control calculation might exceed the
`maximum allowed output power. In these cases the calculated transmit power of all uplink physical channels in this
`timeslot shall be scaled by the same amount in dB before transmission. The total UE transmission power used shall be
`the maximum allowed output power.
`
`The UTRAN may not expect the UE to be capable of reducing its total transmit power below the minimum level
`specified in [2].
`
`4.2.2.2
`
`PRACH
`
`The transmit power for the PRACH is set by higher layers based on open loop power control as described in [15].
`
`4.2.2.3
`
`DPCH, PUSCH
`
`The transmit power for DPCH and PUSCH is set by higher layers based on open loop power control as described in
`[15].
`
`4.2.2.3.1
`
`Gain Factors
`
`Two or more transport channels may be multiplexed onto a CCTrCH as described in [9]. These transport channels
`undergo rate matching which involves repetition or puncturing. This rate matching affects the transmit power required
`to obtain a particular Eb/N0. Thus, the transmission power of the CCTrCH shall be weighted by a gain factor β.
`
`ETSI
`
`Hewlett Packard Enterprise Co. Ex. 1008, Page 9 of 23
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01376
`
`

`

`
`3GPP TS 25.224 version 3.12.0 Release 1999
`
`9
`
`ETSI TS 125 224 V3.12.0 (2002-12)
`
`There are two ways of controlling the gain factors for different TFC’s within a CCTrCH transmitted in a radio frame:
`- β is signalled for the TFC, or
`- β is computed for the TFC, based upon the signalled settings for a reference TFC.
`Combinations of the two above methods may be used to associate β values to all TFC’s in the TFCS for a CCTrCH.
`The two methods are described in sections 4.2.2.3.1.1 and 4.2.2.3.1.2 respectively. Several reference TFC’s for several
`different CCTrCH’s may be signalled from higher layers.
`
`The weight and gain factors may vary on a radio frame basis depending upon the current SF and TFC used. The setting
`of weight and gain factors is independent of any other form of power control. That means that the transmit power PUL is
`calculated according to the formula given in [15] and then the weight and gain factors are applied on top of that, cf.
`[10].
`
`4.2.2.3.1.1
`Signalled Gain Factors
`When the gain factor βj is signalled by higher layers for a certain TFC, the signalled values are used directly for
`weighting DPCH or PUSCH within a CCTrCH. Exact values are given in [10].
`
`4.2.2.3.1.2
`Computed Gain Factors
`The gain factor βj may also be computed for certain TFCs, based on the signalled settings for a reference TFC:
`Let βref denote the signalled gain factor for the reference TFC. Further, let βj denote the gain factor used for the j-th
`TFC.
`
`Define the variable:
`
`K
`
`ref
`
`RM
`
`i
`
`⋅
`
`N
`
`i
`
`
`
`=
`
`∑
`i
`
`where RMi is the semi-static rate matching attribute for transport channel i, Ni is the number of bits output from the
`radio frame segmentation block for transport channel i and the sum is taken over all the transport channels i in the
`reference TFC.
`
`Similarly, define the variable
`
`=
`
`K
`
`j
`
`∑
`i
`
`RM
`
`i
`
`⋅
`
`N
`
`i
`
`
`
`where the sum is taken over all the transport channels i in the j-th TFC.
`
`Moreover, define the variable
`
`L
`
`ref
`
`∑=
`
`i
`
`1
`SF
`i
`
`
`
`where SFi is the spreading factor of DPCH or PUSCH i and the sum is taken over all DPCH or PUSCH i used in the
`reference TFC.
`
`Similarly, define the variable
`
`∑=
`
`L
`
`j
`
`i
`
`1
`SF
`i
`
`
`
`where the sum is taken over all DPCH or PUSCH i used in the j-th TFC.
`The gain factors βj for the j-th TFC are then computed as follows:
`
`KK
`
`ref
`
`j
`
`
`
`×
`
`LL
`
`ref
`
`j
`
`=β
`
`j
`
`No quantisation of βj is performed and as such, values other than the quantised βj given in [10] may be used.
`
`ETSI
`
`Hewlett Packard Enterprise Co. Ex. 1008, Page 10 of 23
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01376
`
`

`

`
`3GPP TS 25.224 version 3.12.0 Release 1999
`
`10
`
`ETSI TS 125 224 V3.12.0 (2002-12)
`
`4.2.2.3.2
`
`Out of synchronisation handling
`
`As stated in 4.2.3.3, the association between TPC commands sent on uplink DPCH and PUSCH, with the power
`controlled downlink DPCH and PDSCH is signaled by higher layers. In the case of multiple DL CCTrCHs it is possible
`that an UL CCTrCH will provide TPC commands to more than one DL CCTrCH.
`
`In the second phase of synchronisation evaluation, as defined in 4.4.2.1.2, the UE shall shut off the transmission of an
`UL CCTrCH if the following criteria are fulfilled for any one of the DL CCTrCHs commanded by its TPC:
`
`- The UE estimates the received dedicated channel burst quality over the last 160 ms period to be worse than a
`threshold Qout, and in addition, no special burst, as defined in 4.5, is detected with quality above a threshold,
`Qsbout. Qout and Qsbout are defined implicitly by the relevant tests in [2]. If the UE detects the beacon channel
`reception level [10 dB] above the handover triggering level, then the UE shall use a 320 ms estimation period for
`the burst quality evaluation and for the Special Burst detection window.
`
`UE shall subsequently resume the uplink transmission of the CCTrCH if the following criteria are fulfilled:
`
`- The UE estimates the received dedicated CCTrCH burst reception quality over the last 160 ms period to be better
`than a threshold Qin or the UE detects a burst with quality above threshold Qsbin and TFCI decoded to be that of
`the Special Burst. Qin and Qsbin are defined implicitly by the relevant tests in [2]. If the UE detects the beacon
`channel reception level [10 dB] above the handover triggering level, then the UE shall use a 320 ms estimation
`period for the burst quality evaluation and for the Special Burst detection window.
`
`4.2.3
`
`Downlink Control
`
`4.2.3.1
`
`P-CCPCH
`
`The Primary CCPCH transmit power is set by higher layer signalling and can be changed based on network conditions
`on a slow basis. The reference transmit power of the P-CCPCH is broadcast on BCH or individually signalled to each
`UE.
`
`4.2.3.2
`
`S-CCPCH, PICH
`
`The relative transmit power of the Secondary CCPCH and the PICH compared to the P-CCPCH transmit power are set
`by higher layer signalling. The PICH power offset relative to the P-CCPCH reference power is signalled on the BCH.
`
`4.2.3.3
`
`SCH
`
`The SCH transmit power is set by higher layer signalling [16]. The value is given relative to the power of the P-
`CCPCH.
`
`4.2.3.4
`
`DPCH, PDSCH
`
`The initial transmission power of the downlink DPCH and the PDSCH shall be set by the network. If associated uplink
`CCTrCHs for TPC commands are signalled to the UE by higher layers (mandatory for a DPCH), the network shall
`transit into inner loop power control after the initial transmission. The UE shall then generate TPC commands to control
`the network transmit power and send them in the TPC field of the associated uplink CCTrCHs. An example on how to
`derive the TPC commands and the definition of the inner loop power control are given in Annex A.1. A TPC command
`sent in an uplink CCTrCH controls all downlink DPCHs or PDSCHs to which the associated downlink CCTrCH is
`mapped to.
`
`In the case that no associated downlink data is scheduled within 15 timeslots before the transmission of a TPC
`command then this is regarded as a transmission pause. The TPC commands in this case shall be derived from
`measurements on the P-CCPCH. An example solution for the generation of the TPC command for this case is given in
`Annex A 1.
`
`Each TPC command shall always be based on all associated downlink transmissions received since the previous related
`TPC command. Related TPC commands are defined as TPC commands associated with the same downlink CCTrCHs.
`If there are no associated downlink transmissions between two or more uplink transmissions carrying related TPC
`commands, then these TPC commands shall be identical and they shall be regarded by the UTRAN as a single TPC
`
`ETSI
`
`Hewlett Packard Enterprise Co. Ex. 1008, Page 11 of 23
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01376
`
`

`

`
`3GPP TS 25.224 version 3.12.0 Release 1999
`
`11
`
`ETSI TS 125 224 V3.12.0 (2002-12)
`
`command. This rule applies both to the case where the TPC commands are based on measurements on the associated
`CCTrCH or, in the case of a transmission pause, on the P-CCPCH.
`
`As a response to the received TPC command, UTRAN may adjust the transmit power. When the TPC command is
`judged as "down", the transmission power may be reduced by the TPC step size, whereas if judged as "up", the
`transmission power may be raised by the TPC step size.
`
`The UTRAN may apply an individual offset to the transmission power in each timeslot according to the downlink
`interference level at the UE.
`
`The transmission power of one DPCH or PDSCH shall not exceed the limits set by higher layer signalling by means of
`Maximum_DL_Power (dB) and Minimum_DL_Power (dB). The transmission power is defined as the average power
`over one timeslot of the complex QPSK symbols of a single DPCH or PDSCH before spreading relative to the power of
`the P-CCPCH.
`
`During a downlink transmission pause, both UE and Node B shall use the same TPC step size which is signalled by
`higher layers. The UTRAN may accumulate the TPC commands received during the pause. TPC commands that shall
`be regarded as identical may only be counted once. The initial UTRAN transmission power for the first data
`transmission after the pause may then be set to the sum of transmission power before the pause and a power offset
`according to the accumulated TPC commands. Additionally this sum may include a constant set by the operator and a
`correction term due to uncertainties in the reception of the TPC bits. The total downlink transmission power at the Node
`B within one timeslot shall not exceed Maximum Transmission Power set by higher layer signalling. If the total
`transmit power of all channels in a timeslot exceeds this limit, then the transmission power of all downlink DPCHs and
`PDSCHs shall be reduced by the same amount in dB. The value for this power reduction is determined, so that the total
`transmit power of all channels in this timeslot is equal to the maximum transmission power.
`
`4.2.3.4.1
`
`Out of synchronisation handling
`
`When the dedicated physical channel out of sync criteria based on the received burst quality is as given in the
`subclause 4.4.2 then the UE shall set the uplink TPC command = "up". The CRC based criteria shall not be taken into
`account in TPC bit value setting.
`
`4.3
`
`Timing Advance
`
`UTRAN may adjust the UE transmission timing with timing advance. The initial value for timing advance (TAphys) will
`be determined in the UTRAN by measurement of the timing of the PRACH. The required timing advance will be
`represented as an 6 bit number (0-63) 'UL Timing Advance' TAul, being the multiplier of 4 chips which is nearest to the
`required timing advance (i.e. TAphys = TAul × 4 chips).
`
`When Timing Advance is used the UTRAN will continuously measure the timing of a transmission from the UE and
`send the necessary timing advance value. On receipt of this value the UE shall adjust the timing of its transmissions
`accordingly in steps of ±4chips. The transmission of TA values is done by means of higher layer messages. Upon
`receiving the TA command the UE shall adjust its transmission timing according to the timing advance command at the
`frame number specified by higher layer signaling. The UE is signaled the TA value in advance of the specified frame
`activation time to allow for local processing of the command and application of the TA adjustment on the specified
`frame. Node-B is also signaled the TA value and radio frame number that the TA adjustment is expected.to take place.
`
`If TA is enabled by higher layers, after handover the UE shall transmit in the new cell with timing advance TA adjusted
`by the relative timing difference ∆t between the new and the old cell:
`TAnew = TAold + 2∆t.
`
`4.4
`
`Synchronisation procedures
`
`4.4.1
`
`Cell Search
`
`During the cell search, the UE searches for a cell and determines the downlink scrambling code, basic midamble code
`and frame synchronisation of that cell. How cell search is typically done is described in Annex C.
`
`ETSI
`
`Hewlett Packard Enterprise Co. Ex. 1008, Page 12 of 23
`Hewlett Packard Enterprise Co. v. Intellectual Ventures II LLC
`IPR2021-01376
`
`

`

`
`3GPP TS 25.224 version 3.12.0 Release 1999
`
`12
`
`ETSI TS 125 224 V3.12.0 (2002-12)
`
`4.4.2 Dedicated channel synchronisation
`
`4.4.2.1
`
`Synchronisation primitives
`
`4.4.2.1.1
`
`General
`
`For the dedicated channels, synchronisation primitives are used to indicate the synchronisation status of radio links,
`both in uplink and downlink. The definition of the primitives is given in the following subclauses.
`
`4.4.2.1.2
`
`Downlink synchronisation primitives
`
`Layer 1 in the UE shall check the synchronization status of each DL CCTrCH individually in every radio frame All
`bursts and transport channels of a CCTrCH shall be taken into account. Synchronisation status is indicated to higher
`layers, using the CPHY-Sync-IND or CPHY-Out-of-Sync-IND primitives. For dedicated physical channels configured
`with Repetition Periods [15 ] only the configured active periods shall be taken into account in the estimation. The status
`check shall also include detection of the Special Bursts defined in 4.5 for DTX.
`
`The criteria for reporting synchronization statu