throbber
3GPP TS 36.213 V8.0.0 (2007-09)
`
`Technical Specification
`
`
`
`3rd Generation Partnership Project;
`Technical Specification Group Radio Access Network;
`Evolved Universal Terrestrial Radio Access (E-UTRA);
`Physical layer procedures
`(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 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.
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2005 (3GPP TS 36.213 v8.0) – 001
`IPR2017-01508
`
`

`

`
`Release 8
`
`2
`
`3GPP TS 36.213 V8.0.0 (2007-09)
`
`
`
`
`
`
`
`
`
`Keywords
`UMTS, radio, layer 1
`
`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.
`
`© 2007, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC).
`All rights reserved.
`
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2005 (3GPP TS 36.213 v8.0) – 002
`IPR2017-01508
`
`

`

`
`Release 8
`
`3
`
`3GPP TS 36.213 V8.0.0 (2007-09)
`
`Contents
`Foreword ............................................................................................................................................................ 5
`1
`Scope ........................................................................................................................................................ 6
`2
`References ................................................................................................................................................ 6
`3
`Definitions, symbols, and abbreviations .................................................................................................. 6
`3.1
`Definitions ............................................................................................................................................................. 6
`3.2
`Symbols ................................................................................................................................................................. 6
`3.3
`Abbreviations ........................................................................................................................................................ 6
`4
`Synchronization procedures ..................................................................................................................... 7
`4.1
`Cell search ............................................................................................................................................................. 7
`4.2
`Timing synchronization ........................................................................................................................................ 7
`4.2.1
`Synchronization primitives ............................................................................................................................. 7
`4.2.2
`Radio link monitoring ..................................................................................................................................... 7
`4.2.3
`Inter-cell synchronization ................................................................................................................................ 7
`4.2.4
`Transmission timing adjustments ................................................................................................................... 7
`5
`Power control ........................................................................................................................................... 7
`5.1
`Uplink power control ............................................................................................................................................ 8
`5.1.1
`Physical uplink shared channel ....................................................................................................................... 8
`5.1.1.1
`UE behaviour ............................................................................................................................................. 8
`5.1.1.2
`eNodeB behaviour ..................................................................................................................................... 9
`5.1.2
`Physical uplink control channel ...................................................................................................................... 9
`5.1.2.1
`UE behaviour ............................................................................................................................................. 9
`5.1.2.2
`eNodeB behaviour ..................................................................................................................................... 9
`5.1.3
`Sounding Reference Symbol ........................................................................................................................... 9
`5.1.2.1
`UE behaviour ............................................................................................................................................. 9
`5.1.2.2
`eNodeB behaviour ..................................................................................................................................... 9
`5.2
`Downlink power allocation ................................................................................................................................... 9
`5.2.1
`UE behaviour ................................................................................................................................................... 9
`5.2.2
`eNodeB behaviour ........................................................................................................................................... 9
`5.2.3
`Downlink channel subcarrier transmit power offset ...................................................................................... 9
`6
`Random access procedure ...................................................................................................................... 10
`6.1
`Physical non-synchronized random access procedure ....................................................................................... 10
`6.1.1
`Timing ........................................................................................................................................................... 10
`6.1.1.1
`Synchronized ........................................................................................................................................... 10
`6.1.1.2
`Unsynchronized ....................................................................................................................................... 10
`6.1.2
`Preamble Sequence selection ........................................................................................................................ 10
`7
`Physical downlink shared channel related procedures ........................................................................... 10
`7.1.
`UE procedure for receiving the physical downlink shared channel .................................................................. 10
`7.2
`UE procedure for reporting channel quality indication (CQI), precoding matrix indicator (PMI) and rank ... 11
`7.2.1
`Channel quality indicator (CQI) definition ................................................................................................... 11
`7.2.2
`Precoding definition ...................................................................................................................................... 11
`8
`Physical uplink shared channel related procedures ................................................................................ 11
`8.1
`eNodeB procedure for receiving physical uplink shared channel ..................................................................... 11
`8.2
`UE sounding procedure ....................................................................................................................................... 11
`8.2.1
`Sounding definition ....................................................................................................................................... 12
`8.3
`UE ACK/NACK procedure ................................................................................................................................ 12
`9
`Physical downlink control channel procedures ...................................................................................... 12
`9.1
`UE procedure for determining physical downlink control channel assignment ................................................ 12
`10
`Physical uplink control channel procedures ........................................................................................... 12
`10.1
`UE procedure for determining physical uplink control channel assignment ..................................................... 12
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2005 (3GPP TS 36.213 v8.0) – 003
`IPR2017-01508
`
`

`

`
`Release 8
`
`4
`
`3GPP TS 36.213 V8.0.0 (2007-09)
`
`Annex A (informative):
`
`
`Change history ............................................................................................... 13
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2005 (3GPP TS 36.213 v8.0) – 004
`IPR2017-01508
`
`

`

`
`Release 8
`
`5
`
`3GPP TS 36.213 V8.0.0 (2007-09)
`
`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 this 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
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2005 (3GPP TS 36.213 v8.0) – 005
`IPR2017-01508
`
`

`

`
`Release 8
`
`6
`
`3GPP TS 36.213 V8.0.0 (2007-09)
`
`Scope
`1
`The present document specifies and establishes the characteristics of the physicals layer procedures in the FDD and
`TDD modes of E-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]
`
`3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
`
`3
`
`Definitions, symbols, and abbreviations
`
`Definitions
`3.1
`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].
`
`(no further definitions)
`
`Symbols
`3.2
`For the purposes of the present document, the following symbols apply:
`
`RB
`scN
`Downlink bandwidth configuration, expressed in units of
`RB
`Uplink bandwidth configuration, expressed in units of
`scN
`
`DL
`RBN
`UL
`RBN
`
`Abbreviations
`3.3
`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].
`
`ACK
`BCH
`CCPCH
`CQI
`CRC
`DL
`DTX
`EPRE
`NACK
`PCFICH
`
`Acknowledgement
`Broadcast Channel
`Common Control Physical Channel
`Channel Quality Indicator
`Cyclic Redundancy Check
`Downlink
`Discontinuous Transmission
`Energy Per Resource Element
`Negative Acknowledgement
`Physical control format indicator channel
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2005 (3GPP TS 36.213 v8.0) – 006
`IPR2017-01508
`
`

`

`
`Release 8
`
`7
`
`3GPP TS 36.213 V8.0.0 (2007-09)
`
`PDSCH
`PHICH
`PRACH
`PUCCH
`PUSCH
`QoS
`RE
`RPF
`RS
`SIR
`SINR
`TA
`TTI
`UE
`UL
`
`
`Physical Downlink Shared Channel
`Physical Hybrid ARQ Indicator Channel
`Physical random access channel
`Physical Uplink Control Channel
`Physical Uplink Shared Channel
`Quality of Service
`Resource Element
`Repetition Factor
`Reference Signal
`Signal-to-Interference Ratio
`Signal to Interference plus Noise Ratio
`Time alignment
`Transmission Time Interval
`User Equipment
`Uplink
`
`4
`
`Synchronization procedures
`
`Cell search
`4.1
`Cell search is the procedure by which a UE acquires time and frequency synchronization with a cell and detects the
`physical layer Cell ID of that cell. E-UTRA cell search supports a scalable overall transmission bandwidth
`corresponding to 72 sub-carriers and upwards.
`
`The following signals are transmitted in the downlink to facilitate cell search: the primary and secondary
`synchronization signals, and the downlink reference signals.
`
`4.2
`
`Timing synchronization
`
`4.2.1
`
`Synchronization primitives
`
`4.2.2
`
`Radio link monitoring
`
`Inter-cell synchronization
`4.2.3
`[For example, for cell sites with a multicast physical channel]
`
`Transmission timing adjustments
`4.2.4
`On receiving a random access burst from a UE the network determines if the UE needs a TA adjustment and if so
`signals to the UE a TA command which is a multiple of 0.52 s and is applied as a 1 step adjustment relative to the
`random access channel preamble transmit timing.
`
`A UE receives TA commands as determined by the network to maintain its time alignment. A TA command received
`by the UE will be a multiple of 0.52 s and is applied as a 1 step adjustment relative to current uplink timing.
`
`Power control
`5
`Power control determines the energy per resource element (EPRE). The term resource element energy denotes the
`energy prior to CP insertion. The term resource element energy also denotes the average energy taken over all
`constellation points for the modulation scheme appl
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2005 (3GPP TS 36.213 v8.0) – 007
`IPR2017-01508
`
`

`

`
`Release 8
`
`8
`
`3GPP TS 36.213 V8.0.0 (2007-09)
`
`Uplink power control
`5.1
`Uplink power control consists of open and closed loop components and controls energy per resource element applied
`for a UE transmission. For intra-cell uplink power control the closed loop component adjusts a set point determined by
`the open loop power control component.
`
`Upon reception of an a-periodic transmit power command in an uplink scheduling grant the UE shall adjust its transmit
`EPRE accordingly.
`
`EPRE is set in the UE.
`
`A cell wide overload indicator (OI) is exchanged over X2 for inter-cell power control.
`
`[Note: Above line regarding OI and X2 to be moved to an appropriate RAN3 spec when it becomes available]
`
`5.1.1
`
`Physical uplink shared channel
`
`UE behaviour
`5.1.1.1
`The setting of the UE Transmit power
`by
`
`P
`pusch
`
` for the physical uplink shared channel (PUSCH) transmissions is defined
`
`P
`pusch
`
`
`
`min(
`
`P
`max
`
`10,
`
`log
`10
`
`(
`
`
` ) PM
`
`o
`
`
`
`
`
`PL
`
`
`
`
`
`f
`
`(
`
`
`
`i
`
`))
`
`
`
`mcs
`
`Where,
`
`
`
` is the maximum allowed power that depends on the UE power class
`
`maxP
` M is the number of assigned resource blocks as indicated in the UL scheduling grant
`
`oP is a UE specific parameter with 1 dB resolution
`  is cell specific path loss compensation factor (can be set to one to allow full path loss compensation) that
`has 8 values from 0.4 to 1 in steps of 0.1 with one of the possible values being zero.
` PL is the downlink pathloss calculated in the UE from a RSRP measurement and signalled RS transmit power
`
` table entries can be set to zero)
` is signaled by RRC ( mcs
`mcs
`o MCS signaled in each UL scheduling grant
`i is a UE specific correction value and is defined differently dependent on scheduling as given by:
`o Scheduled
`
`i is included in each UL scheduling grant
` Function
` signaled via higher layers
`)(f
`
` represents either accumulation or current absolute value
`)(f
`o Not scheduled
`
`i is included in each DL scheduling assignment or jointly coded with other UE specific
`correction values on a TPC PDCCH
` The UE attempts to detect a TPC PDCCH and a DL scheduling frame on every subframe
`except when in DRX.
` The
`i from a DL scheduling assignment overrides any command from a TPC PDCCH
`when both are received in a given subframe.
` Function
` represents accumulation only
`)(f
`
`
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2005 (3GPP TS 36.213 v8.0) – 008
`IPR2017-01508
`
`

`

`
`Release 8
`
`5.1.1.2
`(void)
`
`eNodeB behaviour
`
`9
`
`3GPP TS 36.213 V8.0.0 (2007-09)
`
`5.1.2
`
`Physical uplink control channel
`
`UE behaviour
`5.1.2.1
`The setting of the UE Transmit power
`defined by
`
`P
`pucch
`
` for the physical uplink control channel (PUCCH) transmissions is
`
`P
`pucch
`
`
`
`min(
`
`P
`max
`
`10,
`
`log
`
`10
`
`(
`
`M
`
`pucch
`
`)
`
`
`
`P
`o
`
`_
`
`pucch
`
`
`
`PL
`
`
`
`mcs
`
`_
`
`pucch
`
`(
`g
`
`
`))
`
`
`
`j
`
`where
`
`
`
`
`
`
`
`
`
`pucchM
`
` is the number of assigned resource blocks for the PUCCH
`
`
`
` table entries can be set to zero)
` is signaled by RRC (
`
`mcs _
`mcs _
`pucch
`pucch
`o MCS is signaled using higher layer signaling
` is a UE specific parameter with 1 dB resolution
`
`oP _
`pucch
`j is a UE specific correction value, also referred to as a TPC command, included in a DL scheduling
`assignment or sent jointly coded with other UE specific correction values on a TPC PDCCH.
`o The UE attempts to detect a TPC PDCCH and a DL scheduling frame on every subframe except when
`in DRX.
`o The TPC command from a DL scheduling assignment overrides any command from a TPC PDCCH
`when both are received in a given subframe.
`o Function
` represents accumulation
`)(g
`
`5.1.2.2
`
`eNodeB behaviour
`
`5.1.3
`
`Sounding Reference Symbol
`
`UE behaviour
`5.1.2.1
`The UE Transmit power
`srsP for the SRS is set equal to the PUSCH power level
`
`P
`pusch
`
` plus an offset
`
`P
`offset
`
`_
`
`srs
`
`.
`
`5.1.2.2
`(void)
`
`eNodeB behaviour
`
`Downlink power allocation
`5.2
`The eNodeB determines the downlink transmit energy per resource element.
`
`5.2.1
`
`UE behaviour
`
`5.2.2
`
`eNodeB behaviour
`
`Downlink channel subcarrier transmit power offset
`5.2.3
`[Definition of and restrictions on the subcarrier transmit power offset for each downlink channel type]
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2005 (3GPP TS 36.213 v8.0) – 009
`IPR2017-01508
`
`

`

`
`Release 8
`
`10
`
`3GPP TS 36.213 V8.0.0 (2007-09)
`
`Random access procedure
`6
`Prior to initiation of the non-synchronized physical random access procedure, layer 1 shall receive the following
`information from the higher layers:
`1. Random access channel parameters (number, frequency position, time period, and timing offset)
`2. Available preamble formats and preamble sequence set. Available root Zadoff-Chu (ZC) sequence indices
`3. Preamble transmission r
`
`Physical non-synchronized random access procedure
`6.1
`From the physical layer perspective, the L1 random access procedure encompasses the transmission of random access
`preamble and random access response. The remaining messages are scheduled for transmission by the higher layer on
`the shared data channel and are not considered part of the L1 random access procedure. A random access channel
`occupies 6 resource blocks in a subframe or set of consecutive subframes reserved for random access preamble
`transmissions.
`
`The following steps are required for the L1 random access procedure:
`1. Layer 1 procedure is triggered upon request of a preamble transmission by higher layers.
`2. A preamble sequence is then determined from the preamble sequence set as indicated by higher layers.
`3. A single preamble transmission then occurs using the selected preamble sequence, and the parameters
`indicated by higher layers.
`
`4.
`
`5.
`
`If no response corresponding to the transmitted preamble sequence is detected then the L1 status ("No
`acknowledgment on non-synchronized random access") is passed to the higher layers and the physical random
`access procedure is exited.
`
`If a response corresponding to the transmitted preamble sequence is detected, then the L1 status ("ACK on
`non-synchronized random access received") is passed to the higher layers and the physical random access
`procedure is exited.
`
`6.1.1
`
`Timing
`
`6.1.1.1
`
`6.1.1.2
`
`Synchronized
`
`Unsynchronized
`
`6.1.2
`
`Preamble Sequence selection
`
`7
`
`Physical downlink shared channel related procedures
`
`7.1.
`
`UE procedure for receiving the physical downlink shared
`channel
`[For persistent and non-persistent scheduling, Includes pertinent aspects of downlink HARQ procedure and link
`adaptation procedure including any related signalled parameters to eNodeB and UE, ACK/NACK or CQI repetition
`procedure, eNodeB ACK/NACK detection procedure, handling of multiple HARQ processes for MIMO, etc]
`
`A resource allocation field in each scheduling assignment PDCCH includes two parts. Part 1 indicates how to interpret
`Part 2 of the resource allocation. In a first resource allocation approach, a bitmap indicates the resource block groups
`that are allocated to the scheduled UE. The size of the group is a function of the system bandwidth. In a second resource
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2005 (3GPP TS 36.213 v8.0) – 010
`IPR2017-01508
`
`

`

`
`Release 8
`
`11
`
`3GPP TS 36.213 V8.0.0 (2007-09)
`
`allocation approach, the system bandwidth is divided in subsets of resource blocks, and the resource allocation has the
`capability to indicate one or multiple individual resource blocks to the scheduled UE.
`
`7.2 UE procedure for reporting channel quality indication (CQI),
`precoding matrix indicator (PMI) and rank
`[Includes CQI reporting needed to support frequency domain scheduling at eNodeB, CQI bin bandwidth, selection of
`CQI MCS, repetition, etc]
`
`The time and frequency resources that can be used by the UE to report CQI, PMI, and rank are controlled by the eNB.
`CQI, PMI, and rank reporting is periodic. A UE transmits CQI, PMI, and rank reporting on a PUCCH for subframes
`with no PUSCH transmission and on a PUSCH for those subframes with a scheduled PUSCH transmission.
`
`When reporting rank the UE reports a single rank.
`
`When reporting PMI the UE reports either single or multiple PMI reports. The number of RBs represented by a single
`DL
`RBN or a smaller subset of RBs. The number of RBs represented by a single PMI report is
`UE PMI report can be
`configured by the network.
`
`Channel quality indicator (CQI) definition
`7.2.1
`[Includes definition of CQI information needed for frequency domain scheduling, may define different CQI MCS]
`
`7.2.2
`
`Precoding definition
`
`8
`
`Physical uplink shared channel related procedures
`
`8.1
`
`eNodeB procedure for receiving physical uplink shared
`channel
`[For persistent and non-persistent scheduling, includes pertinent aspects of uplink HARQ and link adaptation procedure
`including any related signalled parameters to eNodeB and UE, repetition, SR procedure, and any uplink reference signal
`sequence assignment procedure]
`
`A resource allocation field in the scheduling grant consists of a resource indication value (RIV) corresponding to a
`starting resource block (
`). The
`) and a length in terms of contiguously allocated resource blocks ( CRBs
`RB
`L
`start
`resource indication value is defined by
`
`2/
`N
`(
`)1
`L
`CRBs
`
`if
`
`(
`
`L
`CRBs
`
`
`
`)1
`
`
`
`UL
`RB
`
` then
`
`RIV
`
`
`
`N
`
`UL
`RB
`
`
`
`
`
`RB
`
`start
`
`
`
`else
`
`RIV
`
`
`
`N
`
`UL
`RB
`
`(
`
`N
`
`UL
`RB
`
`
`
`L
`CRBs
`
`
`
`)1
`
`
`
`(
`
`N
`
`UL
`RB
`
`1
`
`
`RB
`
`)
`
`
`
`start
`
`UE sounding procedure
`8.2
`SRS perodicity and duration, and a comb of RPF=2 are indicated by high layer signalling.
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2005 (3GPP TS 36.213 v8.0) – 011
`IPR2017-01508
`
`

`

`
`Release 8
`
`12
`
`3GPP TS 36.213 V8.0.0 (2007-09)
`
`8.2.1
`
`Sounding definition
`
`8.3
`
`UE ACK/NACK procedure
`
`9
`
`Physical downlink control channel procedures
`
`9.1
`
`UE procedure for determining physical downlink control
`channel assignment
`[includes determining ACK/NACK, CQI, SR physical uplink shared control channel assignments which maybe
`implicitly based on downlink L1/L2 control channel assignments or explicitly signalled]
`
`A UE is required to monitor a set of control channel candidates as often as every sub-frame. The number of candidate
`control channels in the set and configuration of each candidate is configured by the higher layer signaling.
`
`10
`
`Physical uplink control channel procedures
`
`10.1 UE procedure for determining physical uplink control
`channel assignment
`The resource blocks reserved for PUCCHs in a sub-frame are semi-statically configured.
`
`For scheduled PDSCH transmissions, the PUCCH index for ACK/NACK is determined implicitly by a control channel
`index derived from the associated PDCCH.
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2005 (3GPP TS 36.213 v8.0) – 012
`IPR2017-01508
`
`

`

`
`Release 8
`
`13
`
`3GPP TS 36.213 V8.0.0 (2007-09)
`
`Annex A (informative):
`Change history
`
`Change history
`New
`Old
`TSG Doc. CR Rev Subject/Comment
`TSG #
`Date
`0.0.0
`
`
`
` Draft version created
`
`2006-09
`0.0.0 0.1.0
`
`
` Endorsed by RAN1
`
`2006-10
`0.1.0 0.1.1
`
`
`
`Inclusion of decisions from RAN1#46bis and RAN1#47
`
`2007-01
`0.1.1 0.2.0
`
`
` Endorsed by RAN1
`
`2007-01
`0.2.0 0.2.1
`
`
`
`Inclusion of decisions from RAN1#47bis
`
`2007-02
`0.2.1 0.3.0
`
`
` Endorsed by RAN1
`
`2007-02
`
`
` Editor’s version including decisions from RAN1#48 & RAN1#47bis 0.3.0 0.3.1
`
`2007-02
`
`
` Updated Editor’s version
`0.3.1 0.3.2
`
`2007-03
`2007-03 RAN#35 RP-070171
`
`
`For information at RAN#35
`0.3.2 1.0.0
`2007-03
`
`
`
` Random access text modified to better reflect RAN1 scope
`1.0.0 1.0.1
`2007-03
`
`
`
` Updated Editor’s version
`1.0.1 1.0.2
`2007-03
`
`
`
` Endorsed by RAN1
`1.0.2 1.1.0
`2007-05
`
`
`
` Updated Editor’s version
`1.1.0 1.1.1
`2007-05
`
`
`
` Updated Editor’s version
`1.1.1 1.1.2
`2007-05
`
`
`
` Endorsed by RAN1
`1.1.2 1.2.0
`2007-08
`
`
`
` Updated Editor’s version
`1.2.0 1.2.1
`2007-08
`
`
`
` Updated Editor’s version – uplink power control from RAN1#49bis 1.2.1 1.2.2
`2007-08
`
`
`
` Endorsed by RAN1
`1.2.2 1.3.0
`2007-09
`
`
`
` Updated Editor’s version reflecting RAN#50 decisions
`1.3.0 1.3.1
`2007-09
`
`
`
` Updated Editor’s version reflecting comments
`1.3.1 1.3.2
`2007-09
`
`
`
` Updated Editor’s version reflecting further comments
`1.3.2 1.3.3
`2007-09
`
`
`
` Updated Editor’s version reflecting further comments
`1.3.3 1.3.4
`2007-09
`
`
`
` Updated Edtior’s version reflecting further comments
`1.3.4 1.3.5
`2007-09 RAN#37 RP-070731
`
` Endorsed by RAN1
`1.3.5 2.0.0
`2007-09 RAN#37 RP-070737
`
`
`For approval at RAN#37
`2.0.0 2.1.0
`12/09/07 RAN_37 RP-070737
`-
`- Approved version
`2.1.0 8.0.0
`
`
`
`3GPP
`
`HTC CORPORATION, ET AL. v. CELLULAR COMMUNICATIONS EQUIPMENT LLC
`CCE EX2005 (3GPP TS 36.213 v8.0) – 013
`IPR2017-01508
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket