throbber

`
`ETSI TS 125 215 V3.1.1 (2000-01)
`
`Technical Specification
`
`Universal Mobile Telecommunications System (UMTS);
`Physical layer — Measurements (FDD)
`(3G TS 25.215 version 3.1.1 Release 1999)
`
`
`
`
`
`
`
`LGE_0000520
`
`LG Electronlcs Ex. 1008
`
`LGE_0000520
`
`

`

`(3G TS 25.215 version 3.1.1 Release 1999)
`
`1
`
`ETSI TS 125 215 V3.1.1 (2000-01)
`
`
`Reference
`DTS/TSGR-0125215U
`
`
`Keywords
`UMTS
`
`ETSI
`
`Postal address
`
`F-06921 Sophia Antipolis Cedex - FRANCE
`
`Office address
`650 Route des Lucioles - Sophia Antipolis
`Valbonne - FRANCE
`Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
`Siret N° 348 623 562 00017 - NAF 742 0
`Association a but non lucralif enregistrée a la
`Sous-Prefecture de Grasse (06) N° 7803/88
`
`
`Internet
`
`secretariat@etsi.fr
`Individual copies of this ETSI deliverable
`can be downloaded from
`http://www.etsi.org
`If you find errors in the present document, send your
`comment to: editor@etsi.fr
`
`
`Important notice
`
`This ETSI deliverable 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.
`
`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 2000.
`All rights reserved.
`
`LGE_0000521
`
`ETSI
`
`LGE_0000521
`
`

`

`ETSI TS 125 215 V3.1.1 (2000-01)
`2
`(36 T8 25.215 version 3.1.1 Release 1999)
`
`
`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 SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, lPRs notified to ETSI in respect
`ofETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server
`(http://www.etsi.0rg/ipr).
`
`Pursuant to the ETSI IPR Policy, no investigation, including lPR searches, has been carried out by ETSI. No guarantee
`can be given as to the existence of other lPRs not referenced in SR 000 3l4 (or the updates on the ETSI Web server)
`which are, or may be, or may become, essential to the present document.
`
`__—_————————
`
`Foreword
`
`This Technical Specification (TS) has been produced by the ETSI 3'Cl Generation Partnership Project (3GPP).
`
`The present document may refer to technical specifications or reports using their 3GPP identities or GSM identities.
`These should be interpreted as being references to the corresponding ETSI deliverables. The mapping of document
`identities is as follows:
`
`For 3GPP documents:
`
`3G TS | TR nn.nnn "<title>" (with or without the prefix 3G)
`
`is equivalent to
`
`ETSI TS | TR lnn nnn "[Digital cellular telecommunications system (Phase 2+) (GSM);] Universal Mobile
`Telecommunications System; <title>
`
`For GSM document identities of type "GSM xx.yy", e.g. GSM 01.04, the corresponding ETSl document identity may be
`found in the Cross Reference List on wuwetsiorg/kev
`
`LGE_0000522
`
`ETSI
`
`LGE_0000522
`
`

`

`(3G TS 25.215 version 3.1.1 Release 1999)
`
`3
`
`ETSI TS 125 215 V3.1.1 (2000-01)
`
`
`
`Co ntents
`
`Foreword ............................................................................................................................................................ 4
`
`Scope........................................................................................................................................................ 5
`
`References ................................................................................................................................................ 5
`
`1
`
`2
`
`3
`
`4
`
`5
`5.1
`5.1.1
`5.1.2
`5.1.3
`5.1.4
`5.1.5
`5.1.6
`5.1.7
`5.1.8
`5.1.9
`5.1.10
`5.1.11
`5.1.12
`5.1.13
`5.1.14
`5.1.15
`5.2
`5.2.1
`5.2.2
`5.2.3
`5.2.4
`5.2.5
`5.2.6
`5.2.7
`5.2.8
`
`
`
`Abbreviations ........................................................................................................................................... 5
`
`Control of UE/UTRAN measurements ............................................................................................ 6
`
`Measurement abilities for UTRA FDD ....................
`.................................................... 6
`UE measurement abilities .................................................... 6
`
`CPICH RSCP .................................. 7
`PCCPCH RSCP....
`............................................................................... 7
`RSCP ................................................................................................ 7
`SIR ................................... 8
`
`UTRA carrier RSSI.......... 8
`
`
`....................................................... 8
`GSM carrier RSSI
`CPICH Ec/No ............................................................................ 9
`
`..... 9
`Transport channel BLER....
`
`Physical channel BER ......................................................................... 9
`UE transmitted power............................................................................
`10
`
`. 10
`CFN-SFN observed time difference...
`
`
`SFN-SFN observed time difference
`10
`
`UE Rx-Tx time difference ...............................................................................................
`11
`
`Observed time difference to GSM cell ..................................................................................
`11
`
`. 11
`UE GPS Timing of Cell Frames for LCS...
`
`UTRAN measurement abilities ........................
`12
`
`
`RSSI ..................................................................................... 13
`SIR ....................................................................................... 13
`
`Transmitted carrier power ................
`13
`
`Transmitted code power ..................................................................................
`. 14
`
`. 14
`Transport channel BLER.................................................................................
`
`. 14
`Physical channel BER .......
`
`Round trip time .....................................................
`. 15
`
`UTRAN GPS Timing of Cell Frames for LCS
`. 15
`
`Measurements for UTRA FDD ............................
`............................................................... 16
`
`UE measurements ..................................................................... 16
`
`Compressed mode ..................................................................
`. 16
`
`Use of compressed mode/dual receiver for monitoring .............................
`. 16
`
`Parameterisation of the compressed mode.................................................
`16
`Parameterisation limitations ................................................................................................................. 17
`
`6
`6.1
`6.1.1
`6.1.1.1
`6.1.1.2
`6.1.1.3
`
`Annex A (informative): Change history........
`
`..............................................
`
`..........
`
`........................
`
`19
`
`History .............................................................................................................................................................. 20
`
`LGE_0000523
`
`ETSI
`
`LGE_0000523
`
`

`

`(3G TS 25.215 version 3.1.1 Release 1999)
`
`4
`
`ETSI TS 125 215 V3.1.1 (2000-01)
`
`
`
`Foreword
`
`This Technical Specification has been produced by the 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 TS, it will be re-released by the TSG with an identifying
`change of release date and an increase in version number as follows:
`
`Version 3.y.z
`
`where:
`
`x the first digit:
`
`1
`
`presented to TSG for information;
`
`2 presented to TSG for approval;
`
`3
`
`Indicates TSG approved document under change control.
`
`y
`
`z
`
`the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
`updates, etc.
`
`the third digit is incremented when editorial only changes have been incorporated in the specification;
`
`LGE_0000524
`
`ETSI
`
`LGE_0000524
`
`

`

`(3G TS 25.215 version 3.1.1 Release 1999)
`
`5
`
`ETSI TS 125 215 V3.1.1 (2000-01)
`
` 1
`
`Scope
`
`The present document contains the description and definition of the measurements for FDD done at the UE and network
`in order to support operation in idle mode and connected mode
`
` 2
`
`References
`
`The following documents contain provisions which, through reference in this text, constitute provisions of the present
`document.
`
`0 References are either specific (identified by date of publication, edition number, version number, etc.) or
`non-specific.
`
`o For a specific reference, subsequent revisions do not apply.
`
`0 For a non-specific reference, the latest version applies.
`
`[1]
`
`[2]
`
`[3]
`
`[4]
`
`[5]
`
`[6]
`
`[7]
`
`[8]
`
`[9]
`
`[10]
`
`[11]
`
`[12]
`
`[13]
`
`[14]
`
`[15]
`
`[16]
`
`3G TS 25.211: " Physical channels and mapping of transport channels onto physical channels
`(FDD)"
`
`3G TS 25.212: "Multiplexing and channel coding (FDD)"
`
`3G TS 25.213: "Spreading and modulation (FDD)"
`
`3G TS 25.214: "Physical layer procedures (FDD)"
`
`3G TS 25.215: "Physical layer - Measurements (FDD)"
`
`3G TS 25.221: " Physical channels and mapping of transport channels onto physical channels
`(TDD)"
`
`3G TS 25.222: "Multiplexing and channel coding (TDD)"
`
`3G TS 25.223: "Spreading and modulation (TDD)"
`
`3G TS 25.224: "Physical layer procedures (TDD)"
`
`3G TS 25.301: "Radio Interface Protocol Architecture"
`
`3G TS 25.302: "Services provided by the Physical layer"
`
`3G TS 25.303: "UE functions and interlayer procedures in connected mode"
`
`3G TS 25.304: "UE procedures in idle mode"
`
`3G TS 25.331: "RRC Protocol Specification"
`
`3G TR 25.922: "Radio Resource Management Strategies"
`
`3G TR 25.923: "Report on Location Services (LCS)"
`
`
`
`3
`
`Abbreviations
`
`For the purposes of the present document, the following abbreviations apply:
`
`BER
`BLER
`
`chNo
`ISCP
`RL
`
`Bit Error Rate
`Block Error Rate
`
`Received energy per chip divided by the power density in the band
`Interference Signal Code Power
`Radio Link
`
`LGE_0000525
`
`ETSI
`
`LGE_0000525
`
`

`

`(3G TS 25.215 version 3.1.1 Release 1999)
`
`6
`
`ETSI TS 125 215 V3.1.1 (2000-01)
`
`RSCP
`RSSI
`SIR
`
`Received Signal Code Power
`Received Signal Strength Indicator
`Signal to Interference Ratio
`
` 4
`
`Control of UE/UTRAN measurements
`
`In this chapter the general measurement control concept of the higher layers is briefly described to provide an
`understanding on how L1 measurements are initiated and controlled by higher layers.
`
`Ll provides with the measurement specifications a toolbox of measurement abilities for the UE and the UTRAN. These
`measurements can be differentiated in different measurement types: intra-fi‘equency, inter-frequency, inter-system,
`traffic volume, quality and internal measurements (see [14]).
`In the Ll measurement specifications the measurements, see chapter 5, are distinguished between measurements in the
`UE (the messages will be described in the RRC Protocol) and measurements in the UTRAN (the messages will be
`described in the NBAP and the Frame Protocol).
`
`To initiate a specific measurement the UTRAN transmits a ‘measurement control message’ to the UE including a
`measurement ID and type, a command (setup, modify, release), the measurement objects and quantity, the reporting
`quantities, criteria (periodical/event-triggered) and mode (acknowledged/unacknowledged), see [14].
`When the reporting criteria is fulfilled the UE shall answer with a ‘measurement report message’ to the UTRAN
`including the measurement ID and the results.
`In idle mode the measurement control message is broadcast in a System Information.
`
`Intra-frequency reporting events, traffic volume reporting events and UE internal measurement reporting events
`described in [14] define events which trigger the UE to send a report to the UTRAN. This defines a toolbox from which
`the UTRAN can choose the needed reporting events.
`
` 5
`
`Measurement abilities for UTRA FDD
`
`In this chapter the physical layer measurements reported to higher layers (this may also include UE internal
`measurements not reported over the air-interface) are defined.
`
`5.1
`
`UE measurement abilities
`
`The structure of the table defining a UE measurement quantity is shown below:
`
`LGE_0000526
`
`ETSI
`
`LGE_0000526
`
`

`

`(3G TS 25.215 version 3.1.1 Release 1999)
`
`7
`
`ETSI TS 125 215 V3.1.1 (2000-01)
`
`
`‘Comment
`Contains the definition ofthe measurement.
`States if a measurement shall be possible to perform in idle mode and/or Connected mode. For
`connected mode also information of the possibility to perform the measurement on intra-
`frequency and/or inter-frequency are given.
`The following terms are used in the tables:
`Idle = Shall be possible to perform in idle mode
`Connected Intra = Shall be possible to perform in connected mode on an intra-frequency
`Connected Inter = Shall be osslble to perform in connected mode on an inter-freguency
`Gives the ran e and ma
`in
`to bits for the measurements uantil
`.
`
`Column field
`Definition
`Applicable for
`
`
`
`
`5.1.1
`
`CPICH RSCP
`
`Definition
`Received Signal Code Power. the received power on one code measured on the pilot bits of the
`
`Primary CPICH. The reference point for [he RSCP is the antenna connector at the UE.
`
`Applicable for
`Idle. Connected Intro. Connected Inter
`Rangeimapplng
`CPICH RSCP is given with a resolution of 1 dB with the range [~115.
`shall be reported in the unit CPICH_RSCP_LEV where:
`
`-25] dBm. CPICH RSCP
`
`CPICH_RSCP_LEV _00: CPICH RSCP < —115 dBm
`CPICH_RSCP_LEV _01:-115 dBm S CPICH RSCP < —1 14 dBm
`CPICH_RSCP_LEV _02: -114 dBm S CPICH RSCP < —113 dBm
`
`éPICH_RSCP_LEV H89: -27 dBm S CPICH RSCP < -26 dBm
`CPICH_RSCP_LEV ’90: -26 dBm S CPICH RSCP < -25 dBm
`CPICH_RSCP_LEV___§:}1: -25 dBm S CPiCH RSCP
`
`
`
`
`
`
`
`
`5.1.2
`
`PCCPCH RSCP
`
`
`
`Definition
`
`Received Signal Code Power. the received power on one code measured on the PCCPCH from
`a TDD cell. The reference point for the RSCP is the antenna connector at the UE.
`
`Note;
`The RSCP can either be measured on the data part or the midamble of a burst, since there is no
`power difference between these two parts. However, in order to have a common reference,
`measurement on the midamble is assumed.
`
`Applicable for
`Range/mapping
`
`Idle. Connected Inter
`PCCPCH RSCP is given with a resolution of 1 dB with the range [-115.
`RSCP shall be reported in the unit PCCPCH _RSCP_LEV where:
`
`-25] dBm. PCCPCH
`
`PCCPCH _RSCP_LEV _00: PCCPCH RSCP < —115 dBm
`PCCPCH _RSCP_LEV _01: -115 dBm S PCCPCH RSCP < —114 dBm
`PCCPCH _RSCP_LEV _02: -114 dBm S PCCPCH RSCP < —1 13 dBm
`
`RCCPCH _RSCP_LEV _89: -27 dBm s PCCPCH RSCP < -26 dBm
`PCCPCH _RSCP_LEV _90: —26 dBm s PCCPCH RSCP < -25 dBm
`PCCPCH _RSCP_LEV 91: -25 dBm s PCCPCH RSCP
`
`RSCP
`5.1.3
`
`‘Definition
`Received Signal Code Power, the received power on one code measured on the pilot bits of
`the DPCCH after RL combination. The reference point for the RSCP is the antenna connector
`at the UE.
`|Connected Intra
`
`[Applicable for
`
`l
`
`LGE_0000527
`
`ETSI
`
`LGE_0000527
`
`

`

`8
`(3G TS 25.215 version 3.1.1 Release 1999)
`
`
`ETSI TS 125 215 V3.1.1 (2000-01)
`
`Rangelmapplng
`
`
`
`5.1 .4
`
`SIR
`
`Definition
`
`. -40] dBm RSCP is given with
`RSCP is given with a resolution of1 dB with the range [-115, ..
`a resolution of1 dB with the range [—115,
`-25] dBm. RSCP shall be reported in the unit
`RSCP_LEV where:
`
`RSCP_LEV _OO: RSCP < —1 15 dBm
`RSCP_LEV_01: -115 dBm S RSCP < —1 14 dBm
`RSCP_LEV _02: -114 dBm S RSCP < —1 13 dBm
`
`RSCP_LEV __89: -27 dBm s RSCP < -26 dBm
`RSCP_LEV _90: -26 dBm s RSCP < -25 dBm
`RSCP_LEV _91: -25 dBm s RSCP
`
`
`
`Signal to Interference Ratio, defined as: (RSCP/ISCP)x(SF/2). The SIR shall be measured on —|
`DPCCH after RL combination. The reference point for the SIR is the antenna connector of the
`UE.
`
`where:
`
`RSCP = Received Signal Code Power, the received power on one code measured on the pilot
`bits.
`
`ISCP = Interference Signal Code Power, the interference on the received signal measured on the
`pilot bits. Only the non-orthogonal part of the interference is included in the measurement.
`
`SF=The spreading factor used.
`Connected Intra
`SIR Is given with a resolution of 0.5 dB with the range [-11,
`the unit UE_SIR where:
`
`20] dB. SIR shall be reported in
`
`Applicable for
`Rangelmapping
`
`UEHSIRflUO.’ SIR < —11.0 dB
`UEflSIRfi01: -11.0 dB 5 SIR < —10.5 dB
`UE*81R#022-10.5 dB S SIR < —10.0 dB
`
`I.J-E__S|R_61: 19.0 dB 5 SIR < 19.5 dB
`UE_S|R_62: 19.5 dB 3 SIR < 20.0 dB
`UE_SIR_63: 20.0 dB 4.; SIR
`
`
`
`
`
`
`
`
`UTRA carrier RSSI
`5.1.5
`
`Definition
`Received Signal Strength Indicator. the wide-band received power within the relevant channel
`bandwidth. Measurement shall be performed on a UTRAN downlink carrier. The reference point
`
`for the RSSI is the antenna connector al the UE.
`Applicable for _‘tglleLgonnected lntra. Connected Inter
`
`UTRA carrier RSSI is given with a resolution of 1 dB with the range [—94.
`-32] dBm. UTRA
`Range/mapping
`carrier RSSI shall be reported in the unit UTRA_carrier_RSSl_LEV where.
`
`UTRA_carrier_RSSl_LEV _00: UTRA carrier RSSI < —94 dBm
`UTRA_carrier_RSSl_LEV _01: -94 dBm s UTRA carrier RSSI < —93 dBm
`UTRA_carrier_RSSl_LEV _02: -93 dBm s UTRA carrier RSSI < —92 dBm
`
`UTRA_carrier_RSSlgLEV H61: -32 dBm S UTRA carrier RSSI < -33 dBm
`UTRA_carrier_RSSl_LEV _62: -33 dBm s UTRA carrier RSSI < -32 dBm
`UTRA_carrier_RSSl_LEVJggz -32 dBm s UTRA carrier RSSI
`
`5.1.6
`
`GSM carrier RSSI
`
`LGE_0000528
`
`ETSI
`
`LGE_0000528
`
`

`

`(3G TS 25.215 version 3.1.1 Release 1999)
`
`9
`
`ETSI TS 125 215 v3.1.1 (2000-01)
`
`
`
`Definition
`Received Signat Strength Indicator. the wide-band received power within the relevant channel
`
`
`
`bandwidth. Measurement shall be performed on a GSM BCCH carrier. The reference point for
`
`
`the R88! is the antenna connector at the UE.
`
`- licable for
` A -
`Idle Connected Inter
`
`to the definition of RXLEV in GSM 05.08.
`
`
`
`
`
`
`
`CPICH EC/No
`5.1.7
`
`
`Definition
`
`
`
`
`Rangetmapping
`
`The received energy per chip divided by the power density in the band. The Ec/No is identical to
`RSCP/RSSI. Measurement shall be performed on the Primary CPICH. The reference point for
`EcINo is the antenna connector at the UE.
`Idle. Connected Intra. Connected inter
`CPICH Ecr’No is given with a resolution of 1 dB with the range [-24,
`be reported in the unit CPICH_Ec/No where:
`
`0] dB. CPICH EcrNo shall
`
`CPICH_ECJ'N0 _00: CPICH Ec/No < —24 dB
`CPICH_ECINO _011-24 dB 5 CPICH EC/No < —23 dB
`CPICH_EC!NO _02: -23 dB S CPICH Ec/No < —22 dB
`
`carol-tjcrrvo _23: -2 dB 3 CPICH Ec/No < -1 dB
`cprcejcrtvo _24: -1 dB 3 CPICH Ec/No < 0 dB
`oprcn_Eeng_25; 0 dB 3 CPICH Ec/No
`
`
`
`
`
`
`
`
`
`Transport channel BLER
`5.1.8
`
`Definition
`Estimation of the transport channel block error rate (BLER). The BLER estimation shall be based
`on evaluating the CRC on each transport block after RL combination. BLER estimation is only
`required for transport channels containing CRC. In connected mode the BLER shall be possible
`to measure on any transport channel. If requested in idle mode it shall be possible to measure
`
`the BLER on transport channel PCH.
`
`Idle. Connected Intra
`Applicable for
`Range/mapping
`The Transport channel BLER shall be reported for O 5 Transport channel BLER s 1 in the unit
`BLER_dB where:
`
`
`
`BLER_dB_OO: Transport channel BLER = O
`BLER_dB_01: -oo < Log10(Transport channel BLER) < —4.03
`BLER_dB_02: -4.03 s Log10(Transport channel BLER) < -3.965
`BLER_dB_03: -3.965 S Log10(Transport channel BLER) < -3.9
`
`BLER_dB_61: -o.195 s Log10(Transport channel BLER) < -o.13
`BLER_dB_62: -O.13 s Log10(Transport channel BLER) < -0.065
`BLER_dB_63: -0.065 s Log10(Transport channel BLER) s 0
`
`5.1.9
`
`Definition
`
`Applicable for
`
`Physical channel BER
`
`
`The physical channel BER is an estimation of the average bit error rate (BER) before channel
`decoding of the DPDCH data after RL combination. At most it shall be possible to report a
`physical channel BER estimate at the end of each Tl‘l for the transferred TrCh's, e.g. for TrCh's
`with a 'l'l'l of x ms a x ms averaged physical channel BER shall be possible to report every x ms.
`IConnected lntra
`
`_]
`
`LGE_0000529
`
`ETSI
`
`LGE_0000529
`
`

`

`(3G TS 25.215 version 3.1.1 Release 1999)
`
`10
`
`ETSI TS 125 215 v3.1.1 (2000.01)
`
`
`Range/mapping
`
`The Physical channel BER shall be reported for 0 5 Physical channel BER S 1 in the unit
`BER_dB where:
`
`BER_dB_OO: Physical channel BER = 0
`BER_dB_01: -<>o < Log10(Physica| channel BER) < -4.03
`BER_dB_02: -4.03 s Long(Physica| channel BER) < -3.965
`BER_dB_O3: -3.965 s Log10(Physica| channel BER) < -3.9
`
`BER_dB_61: -O.195 s Log10(Physica| channel BER) < -0.13
`BER_dB_62: -0.13 S Log10(Physical channel BER) < -0.065
`
`BER_dB_63: -0.065 s Log10tPhysical channel BER) s O
`
`UE transmitted power
`5.1.10
`
`Definition
`The total UE transmitted power on one carrier. The reference point for the UE transmitted power
`
`shall be the UE antenna connector.
`
`
`Applicable for
`Range/mapping
`
`Connected Intra
`UE transmitted power is given with a resolution of1 dB with the range [-50,
`transmitted power shall be reported in the unit UE_TX_POWER where:
`
`33} dBm. LIE
`
`UE_TX_POWER _021: -50 dBm s UE transmitted power < —49 dBm
`UE_TX_POWER _022: -49 dBm s UE transmitted power < —48 dBm
`UE_TX_POWER _023: -48 dBm s UE transmitted power < —47 dBm
`
`UE_TX_POWER _102 31 dBm s UE transmitted power < 32 dBm
`UE_TX_POWER _103: 32 dBm s UE transmitted power < 33 dBm
`UE_TX POWER _104: 33 dBm s UE transmitted powar < 34 dBm
`
`
`
`
`
`
`
`
`
`CFN-SFN observed time difference
`5.1.11
`
`Definition
`The CFN-SFN observed time difference to cell is defined as: OFFx38400+ Tm, where:
`Tm= TRxsFN - (Tum-To). given in chip units with the range [0, 1,
`38399] chips
`TUETx is the time when the UE transmits an uplink DPCCH/DPDCH frame.
`To is defined in TS 25.211 section 7.1.3.
`TRxSFN is time at the beginning of the next received neighbouring P-CCPCH frame after the time
`instant TUETx-Toin the UE. If the next neighbouring P-CCPCH frame is received exactly at TUETX'
`T0 then TRxSFN=TUETx-T0 (which leads to Tm=0)
`and
`255] frames
`OFF=(CFNTx-SFN) mod 256, given in number of frames with the range [0, 1.
`CFNTx is the connection frame number for the UE transmission of an uplink DPCCHlDPDCH
`frame at the time TUETx.
`SFN = the system frame number for the neighbouring P-CCPCH frame received in the UE at the
`time TRxSFN.
`
`In case the inter-frequency measurement is done with compressed mode, the value for the
`parameter OFF is always reported to be 0.
`In case that the SFN measurement indicator indicates that the UE does not need to read cell
`SFN of the target neighbour cell. the value of the parameter OFF is always be set to 0.
`
`
`Note: In Compressed mode it is not required to read cell SFN of the target neighbour cell.
`',Connected Inter. Connected Intra
`
`Time difference is given with the resolution of one chip with the range [0,
`9830399} chips.
`
`Applicable for
`Range/mapping
`
`5.1.12
`
`SFN-SFN observed time difference
`
`LGE_0000530
`
`ETSI
`
`LGE_0000530
`
`

`

`ETSI TS 125 215 v3_1,1 (2000.01)
`11
`(3G TS 25.215 version 3.1.1 Release 1999)
`
`
`Definition
`
`Ter 1:
`The SFN-SFN observed time difference to cell is defined as: OFFx38400+ Tm. where:
`Tm= TRxsFNi - TRxSFNj, given in chip units with the range [0. 1,
`38399] chips
`TRxSFNj is the time at the beginning of a received neighbouring P-CCPCH frame from cell j.
`TRxSFNi
`is time at the beginning of the next received neighbouring P-CCPCH frame from cell i
`after the time instant TRxSFNj in the UE. If the next neighbouring P-CCPCH frame is received
`exactly at TRxSFNj then TRxsFNj= TRxsFNi (which leads to Tm=0)
`and
`255] frames
`OFF=(SFN,~- SFNi) mod 256. given in number of frames with the range [0, 1.
`SFNj = the system frame number for downlink P-CCPCH frame from cellj in the UE at the time
`TRxSFNj-
`SFNI = the system frame number for the P-CCPCH frame from cell i received in the UE at the
`time TRxSFNi-
`Tyge 2:
`The relative timing difference between cellj and cell i, defined as TCPICHij - TcPchin, where:
`TCPICHij is the time when the UE receives one Primary CPICH slot from cellj
`TCPlCHin is the time when the UE receives the Primary CPICH slot from cell ithat is closest in
`time to the Primary CPICH slot received from cell]
`Type 1: idle. Connected Intra
`_
`Type 2: Idle, Connected Intra. Connected Inler
`Tyge 1: Time difference is given with a resolution of one chip with the range [0,
`chips.
`Type 2: Time difference is given with a resolution of 0.25 chip with the range [-1279.75.
`1280! chips.
`
`9830399]
`
`
`
`
`
`Applicable for
`
`Range/mapping
`
`Definition
`
`5.1.13 UE Rx-Tx time difference
`
`The difference in time between the UE upiink DPCCHJDPDCH frame transmission and the first
`significant path. ofthe downlink DPCH frame from the measured radio link. Measurement shall
`be made for each cell included in the active set.
`Note: The definition of "first significant path" needs further elaboration.
`
`
`
`Connected Intra
`
`A plicable for
`
`
`Range/mapping
`The UE Rx—Tx time difference is given with the resolution of 0.25 chip with the range [876,
`
`
`
`1172 chi s.
`
`
`
`
`
`5.1.14 Observed time difference to GSM cell
`
`Definition
`The Observed time difference to GSM cell is defined as: TRszMj - TRxsFNi, where:
`TRxSFNi
`is the time at the beginning of the P-CCPCH frame with SFN=0 from cell i
`TRxGSMj
`is the time at the beginning of the GSM BCCH 51-multiframe from GSM frequency]
`received closest in time after the time TRxSFNi. If the next GSM multiframe is received exactly at
`TRxsFNi then Taxesw =TRxSFNi (which leads to TRxGSMj - TRxeri = 0) The timing measurement shall
`reflect the timing situation when the most recent (in time) P-CCPCH with SFN=0 was received in
`the UE.
`Idle. Connected Inter
`Agplicable for
`The Observed time difference to GSM cell is given with the resolution of 3060it4096'13} ms with
`Rangeimapping
`
`jlhe ra nge to. .. .. 3060113-3060ii4095‘1QiLms.
`
`
`
`
`5.1.15 UE GPS Timing of Cell Frames for LCS
`
`
`Definition
`
`The timing between cell j and GPS Time Of Week. TUE-GPS] is defined as the time of
`occurrence of a specified UTRAN event according to GPS time. The specified UTRAN event
`is the beginning of a particular frame (identified through its SFN) in the first significant
`multipath of the cell j CPICH, where cell j is a cell within the active set.
`
`Apfilicable for
`‘ Connected Intra, Connected Inter
`Range/mapping —|" The resolution 0fTUE.Gst is luS. The range is from 0 to 6.04><10ll uS.
`
`
`
`LGE_0000531
`
`ETSI
`
`LGE_0000531
`
`

`

`(3G TS 25.215 version 3.1.1 Release 1999)
`
`12
`
`ETSI TS 125 215 V3.1.1 (2000-01)
`
`5.2
`
`UTRAN measurement abilities
`
`The structure of the table defining a UTRAN measurement quantity is shown below:
`
`LGE_0000532
`
`ETSI
`
`LGE_0000532
`
`

`

`ETSI TS 125 215 V3.1.1 (2000-01)
`13
`(3G TS 25.215 version 3.1.1 Release 1999)
`
`
`Column field
`Comment
`Definition
`COntains the definition ofthe measurement.
`
`Range/mapping
`Gives the range and mapping to bits for the measurements quantity.
`
`
`
`
`
`
`
`
`5.2.1 RSSI
`
`Definition
`
`Range/mapping
`
`Received Signal Strength indicator, the wide-band received power within the UTRAN uplink
`carrier channel bandwidth in an UTRAN access point. The reference point for the RSSI
`measurements shall be the antenna connector.
`RSSI is given with a resolution of 0.5 dB with the range [-105,
`reported in the unit RSSI_LEV where:
`
`—74] dBm. RSSI shall be
`
`RSSIfiLEV _00: RSSI < —105.0 dBm
`RSSI_LEV _01: -105.0 dBm S RSSI < —104.5 dBm
`RSSI_LEV _02: -104.5 dBm S RSSI < —104.0 dBm
`
`RSSI_LEV _61: -73.0 dBm s RSSI < -73.5 dBm
`RSSI_LEV _62: -73.5 dBm s RSSI < -74.0 dBm
`__RSS| LEV 63: -74.0 dBm s RSSI
`
`SIR
`5.2.2
`
`
`Definition
`
`Range/mapping
`
`
`
`
`SF=The spreading factor used on the DPCCH.
`SIR is given with a resolution of 0.5 dB with the range [-11,
`the unit UTRAN_SIR where:
`
`Signal to interference Ratio, is defined as: (RSCP/ISCP)><SF. Measurement shall be performed
`on the DPCCH after RL combination in Node B. The reference point for the SIR measurements
`shall be the antenna connector.
`
`where:
`
`RSCP = Received Signal Code Power. the received power on one code.
`
`ISCP = Interference Signal Code Power, the interference on the received signal. Only the non-
`orthogonai part of the interference is included in the measurement.
`
`20] dB. SIR shall be reported in
`
`UTRAN_S|R_00: SIR < —11.0 dB
`UTRAN_S|R_01: -11.0 dB 5 SIR < —10.5 dB
`UTRAN_S|R_02: -10.5 dB 5 SIR < —10.0 dB
`
`UTRAN_S|R_61: 19.0 dB 3 SIR < 19.5 dB
`UTRAN_S|R_62: 19.5 dB 5 SIR < 20.0 dB
`UTRAN_S|R_63: 20.0 dB 3 SIR
`
`
`
`
`
`5.2.3 Transmitted carrier power
`Definition
`Transmitted carrier power, is the total transmitted power on one carrier from one UTRAN access '
`point. Measurement shall be possible on any carrier transmitted from the UTRAN access point.
`The reference point for the total transmitted power measurement shall be the antenna connector.
`in case of Tx diversity the total transmitted power for each branch shall be measured.
`
`
`
`LGE_0000533
`
`ETSI
`
`LGE_0000533
`
`

`

`ETSI TS 125 215 V3.1.1 (2000-01)
`14
`(3G TS 25.215 version 3.1.1 Release 1999)
`
`Rangelmapping
`50] dBm
`Transmitted carrier power is given with a resolution of 0.5 dB with the range [0,
`Transmitted carrier power shall be reported in the unit UTRAN_TXfiPOWER where:
`
`
`
`UTRAN_TXfiPOWER _016: 0.0 dBm S Transmitted carrier power < 0.5 dBm
`UTRAN_TX_POWER _017: 0.5 dBm S Transmitted carrier power < 1.0 dBm
`UTRAN_TX_POWER _018: 1.0 dBm S Transmitted carrier power < 1.5 dBm
`
`UTRAN_TX_POWER _114: 49.0 dBm S Transmitted carrier power < 49.5 dBm
`UTRAN_TX_POWER _115: 49.5 dBm S Transmitted carrier power < 50.0 dBm
`UTRAN_TX_POWER _116: 50.0 dBm S Transmitted carrier power < 50.5 dBm
`
`
`
`5.2.4 Transmitted code power
`
`Definition
`Transmitted code power, is the transmitted power on one channeltsation code on one given
`scrambling code on one given carrier. Measurement shall be possible on any DPCH transmitted
`from the UTRAN access point and shall reflect the power on the pilot bits of the DPCH. The
`reference point forthe transmitted code power measurement shall be the antenna connector. In
`case of Tx diversity the transmitted code power for each branch shall be measured.
`Range/mapping
`Transmitted code power is given with a resolution of 0.5 dB with the range [—10,
`46] dBm.
`Transmitted code power shall be reported in the unit UTRAN_CODE_POWER where:
`
`
`
`UTRAN_CODE_POWER _010: -10.0 dBm S Transmitted code power < -9.5 dBm
`UTRAN_CODE_POWER _011: -9.5 dBm S Transmitted code power < -9.0 dBm
`UTRAN_CODE_POWER _012: -9.0 dBm S Transmitted code power < -8.5 dBm
`
`UTRAN_CODE_POWER _120: 45.0 dBm s Transmitted code power < 45.5 dBm
`UTRAN_CODE_POWER _121: 45.5 dBm S Transmitted code power < 46.0 dBm
`UTRAN_CODE_POWER 122: 46.0 dBm S Transmitted code power < 46.5 dBm
`
`
`
`
`
`5.2.5 Transport channel BLER
`
`
`
`[Definition
`
`Range/mapping
`
`
`
`
`
`Estimation ofthe transport channel biock error rate (BLER). The BLER estimation shalt be based
`on evaluating the CRC on each transport block. Measurement shall be possible to perform on
`any transport channel after RL combination in Node B. BLER estimation is only required for
`_ _
`transport channels containing CRC.
`The Transport channel BLER shall be reported for 0 S Transport channel BLER S 1 in the unit
`BLERgdB where:
`
`BLER_dB_OO: Transport channel BLER = 0
`BLER_dB_01: -oo < Log10(Transport channel BLER) < -4.03
`BLER_dB_OZ: -4.03 S Log10(Transport channel BLER) < -3.965
`BLER_dB_OS: -3.965 S Log10(Transport channel BLER) < -3.9
`
`BLER_dB_61: -0.195 S Log10(Transport channel BLER) < -0.13
`BLER_dB_62: -0.13 S Log10(Transport channel BLER) < -0.065
`BLER_dB_63: -0.065 S Log10(Transport channel BLER) S 0
`
`
`
`5.2.6
`
`Physical channel BER
`
`LGE_0000534
`
`ETSI
`
`LGE_0000534
`
`

`

`(3G TS 25.215 version 3.1.1 Release 1999)
`
`15
`
`ETSI TS 125 215 V3.1.1 (2000-01)
`
`Definition
`
`Range/mapping
`
`
`
`IType 1:
`Measured on the DPDCH:
`The physical channel BER is an estimation of the average bit error rate (BER) before channel
`decoding of the DPDCH data after RL combination in Node B.
`
`Type 2:
`Measured on the DPCCH:
`The Physical channel BER is an estimation of the average bit error rate (BER) on the DPCCH
`after RL combination in Node B.
`
`It shall be possible to report a physical channel BER estimate of type 1 or of type 2 or of both
`types at the end of each TTI for the transferred TrCh's, e.g. for TrCh's with a 'I'I'I of x ms a x ms
`averagedphysical channel BER shall be possible to report every X ms.
`The Physical channel BER shall be reported for 0 5 Physical channel BER S 1 in the unit
`BERWdB where:
`
`BER_dB_OO: Physical channel BER = 0
`BER_dB_O1: -oo < Log10(Physical channel BER) < -4.03
`BER_dB_02: -4.03 s Log10(Physical channel BER) < -3.965
`BER_dB_OS: -3.965 s Log10(Physica| channel BER) < -3.9
`
`
`
`I
`
`

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