hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
f0d098a37eb34f0b432bf0e46089ec9a
|
30.821
|
3.3.1 UTRAN Self-Organizing Networks (SON) management (OAM-SON-UTRAN) UID_510059
|
3GPP TSG SA Meeting #53 SP-110518
Fukoka, Japan; 19-21 Sep 2011
3GPP TSG SA WG5 (Telecom Management) Meeting #78 S5-112587
22 - 26 August 2011; Istanbul, Turkey revision of S5-112325
|
f0d098a37eb34f0b432bf0e46089ec9a
|
30.821
|
3.3.2 LTE Self-Organizing Networks (SON) coordination management (OAM-SON-COOR) UID_510051
|
3GPP TSG SA Meeting #53 SP-110522
Fukoka, Japan; 19-21 Sep 2011
3GPP TSG SA WG5 (Telecom Management) Meeting #78 S5-112711
22 - 26 August 2011; Istanbul, Turkey revision of S5-112708
|
f0d098a37eb34f0b432bf0e46089ec9a
|
30.821
|
4 Charging Management small Enhancements (CH11) UID_510052
| |
f0d098a37eb34f0b432bf0e46089ec9a
|
30.821
|
4.1 Add solutions for Rc - reference point within the Online Charging System (OCS) (CH-Rc) UID_470045 Moved from Rel-10
|
TSG SA Meeting #51 SP-110129
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-111437
Meeting SA5#76, 28 February - 4 March 2011, San Diego, USA revision of SP-100078
Technical Specification Group Services and System Aspects TSGS#47(10)0078
Meeting #47; Vienna, Austria; 22-25 March 2010
3GPP TSG-SA5 (Telecom Management) S5-100993
Meeting SA5#70, 1 - 5 Mar 2010, Xiamen, China revision of S5-100822
|
f0d098a37eb34f0b432bf0e46089ec9a
|
30.821
|
4.2 Charging for Policy Enhancements for Sponsored Connectivity and Coherent Access to Policy related Data Bases (PEST-CH) UID_510060
|
TSG SA Meeting #51 SP-110127
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-110535
SA5#75, 24 - 28 Jan 2011; Sorrento, ITALY revision of SP-110502
TSG SA Meeting #51 SP-110126
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-111374
SA5#76, 28 Feb - 4 Mar 2011; San Diego, USA revision of S5-111309 3GPP Work Area *
Radio Access
X
Core Network
Services
|
f0d098a37eb34f0b432bf0e46089ec9a
|
30.821
|
5 Transit Inter Operator Identifier for IMS Interconnection Charging in multi operator environment (IOI_IMS_CH) UID_510029
|
TSG SA Meeting #51 SP-110132
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-110422
SA5#75, 24 - 28 Jan 2011; Sorrento, ITALY revision of S5-110248
|
f0d098a37eb34f0b432bf0e46089ec9a
|
30.821
|
6 Studies
| |
f0d098a37eb34f0b432bf0e46089ec9a
|
30.821
|
6.0 Study on Usage Monitoring Control Enhancement (FS_UMONC) UID_520035
|
TSG SA Meeting #51 SP-110349
Bratislava, Slovakia, 06 - 08 June, 2011
|
f0d098a37eb34f0b432bf0e46089ec9a
|
30.821
|
6 MMI Aspects
|
N/A
|
f0d098a37eb34f0b432bf0e46089ec9a
|
30.821
|
6.1 Study on version handling (FS_OAM_VH) UID_470050 Moved from Rel-10
|
Technical Specification Group Services and System Aspects TSGS#47(10)0082
Meeting #47; Vienna, Austria; 22-25 March 2010
3GPP TSG-SA5 (Telecom Management) S5-100338
Meeting SA5#70, 1-5 Mar 2010, Xiamen, P.R. China
|
f0d098a37eb34f0b432bf0e46089ec9a
|
30.821
|
6.2 Study on Management of Converged Networks (FS_ManCon) UID_480047 Moved from Rel-10
| |
f0d098a37eb34f0b432bf0e46089ec9a
|
30.821
|
6.3 Study on User Data Convergence (UDC) information model handling and provisioning: Example Use Cases (FS_UDC_AppUseCase) UID_490039 Moved from Rel-10
| |
f0d098a37eb34f0b432bf0e46089ec9a
|
30.821
|
6.4 Study on OAM aspects of inter-RAT Energy Saving (FS_OAM_ES_iRAT) UID_510045
|
TSG SA Meeting #51 SP-110138
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-111491
Meeting SA5#76, 28 Feb – 4 March 2011, San Diego, USA revision of S5-111342
|
f0d098a37eb34f0b432bf0e46089ec9a
|
30.821
|
6.5 Study on management of Heterogeneous Networks (FS_OAM_HetNet) UID_510046
|
TSG SA Meeting #51 SP-110140
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-111492
SA5#76, 28 Feb - 4 Mar 2011; San Diego, USA revision of S5-111345
|
db79454f376b7d1b792302faef07c1bd
|
32.791
|
32.791 Common Radio Access Technology (RAT) Network Resource Model (NRM) Integration Reference Point (IRP): Requirements
| |
db79454f376b7d1b792302faef07c1bd
|
32.791
|
32.792 Common Radio Access Technology (RAT) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)
| |
db79454f376b7d1b792302faef07c1bd
|
32.791
|
32.796 Common Radio Access Technology (RAT) Network Resource Model (NRM) Integration Reference Point (IRP): Solution Set (SS) definitions
| |
db79454f376b7d1b792302faef07c1bd
|
32.791
|
1 Scope
|
The present document defines, in addition to the requirements defined in 3GPP TS 32.101 [2], 3GPP TS 32.102 [3] and 3GPP TS 32.600 [4], the Requirements for the Common RAT NRM IRP for equipment that may be shared between BSS in GSM, UTRAN and E‑UTRAN.
The present document can be used also for managing the equipment that can be shared by several RATs, even in the cases when it is not being shared.
|
db79454f376b7d1b792302faef07c1bd
|
32.791
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
[3] 3GPP TS 32.102: "Telecommunication management; Architecture".
[4] 3GPP TS 32.600: "Telecommunication management; Configuration Management (CM); Concept and high-level requirements".
[5] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions".
|
db79454f376b7d1b792302faef07c1bd
|
32.791
|
3 Definitions and abbreviations
| |
db79454f376b7d1b792302faef07c1bd
|
32.791
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in 3GPP TS 32.150 [5], 3GPP TS 32.101 [2], 3GPP TS 32.102 [3] and 3GPP 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 3GPP TS 32.150 [5], 3GPP TS 32.101 [2], 3GPP TS 32.102 [3] and 3GPP TR 21.905 [1], in this order.
|
db79454f376b7d1b792302faef07c1bd
|
32.791
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
BSS Base Station Subsystem
CAPEX Capital Expenditure
E-UTRAN Evolved UTRAN
GSM Global System for Mobile communications
IRP Integration Reference Point
NRM Network Resource Model
RAN Radio Access Network
RAT Radio Access Technology
UTRAN Universal Terrestrial Radio Access Network
|
db79454f376b7d1b792302faef07c1bd
|
32.791
|
4 Concepts and background
|
It becomes more and more common that operators operate more than one RAT. To save CAPEX, some radio equipment can be shared between the different RATs. Radio equipment can also be shared within a RAT. This NRM makes it easy to operate such shared radio equipment and to understand the consequences in all affected RATs when a change is made in a shared equipment.
|
db79454f376b7d1b792302faef07c1bd
|
32.791
|
5 Requirements
|
The following general and high-level requirement applies for the present IRP:
A. IRP-related requirements in 3GPP TS 32.101 [2].
B. IRP-related requirements in 3GPP TS 32.102 [3].
C. IRP-related requirements in 3GPP TS 32.600 [4].
In addition to the above, the following more specific requirements apply:
REQ-GRAN_NRM-CON-001: The NRM defined by this IRP shall contain IOCs and related definitions, supporting equipment that may be shared between BSS, UTRAN and E-UTRAN networks.
REQ-GRAN_NRM-CON-002: The IRPAgent shall support a capability allowing the IRPManager to know which RATs are served by each managed object.
Annex A (informative):
Change history
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
2010-12
SP-50
SP-100769
Submitted to SA#50 for Information
0.1.1
1.0.0
2011-03
SP-51
SP-110178
--
--
Presentation to SA for Approval
1.0.0
2.0.0
2011-03
--
--
--
--
Publication
2.0.0
10.0.0
2012-09
-
-
-
-
Update to Rel-11 version (MCC)
10.0.0
11.0.0
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
1 Scope
|
This present document specifies the measurement procedure for the conformance test of the mobile station that contain transmitting characteristics, receiving characteristics and performance requirements in addition to requirements for support of RRM (Radio Resource Management) in both UTRATDD modes. The two options are the 3,84 Mcps TDD Option and 1,28 Mcps TDD Option, respectively.
The requirements are listed in different clauses only if the corresponding parameters deviate. More generally, tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the “definition and applicability” part of the test.
For example only release 5 and later UE declared to support HSDPA shall be tested for this functionality. In the event that for some tests different conditions apply for different releases, this is indicated within the text of the test itself.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TS 25.102 (V4.0.0): "UTRA (UE) TDD; Radio Transmission and Reception (TDD)".
[2] 3GPP TS 25.123: "Requirements for Support of Radio Resource Management (TDD)".
[3] 3GPP TS 34.108 "Common Test Environments for User Equipment (UE) Conformance Testing"
[4] 3GPP TS 34.109: "Terminal logical test interface; Special conformance testing functions".
[5] 3GPP TS 25.224: "Physical Layer Procedures (TDD)".
[6] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[7] 3GPP TR 25.990: "Vocabulary".
[8] ITU-R Recommendation SM.328-9: "Spectra and bandwidth of emissions".
[9] 3GPP TS 25.331: "Radio Resource Control (RRC) Protocol Specification".
[10] 3GPP TS 25.433 "UTRAN Iub Interface NBAP Signalling".
[11] ITU-R Recommendation SM.329: "Spurious emissions".
[12] 3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode".
[13] 3GPP TS 25.303: "Interlayer Procedures in Connected Mode".
[14] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification".
[15] 3GPP TS 25.223: "Spreading and modulation (TDD)".
[16] ETSI ETR 273-1-2: "Improvement of radiated methods of measurement (using test sites) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measuremement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes".
[17] 3GPP TR 25.926: "UE Radio Access Capabilities".
[18] 3GPP TR 21.904: "UE capability requirements".
[19] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)".
[20] 3GPP TS 45.008: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control".
[21] 3GPP TS 34.123-1: "User Equipment (UE) Conformance Specification; Part 1: Protocol Conformance Specification".
[22] 3GPP TS 25.225: "Physical Layer – Measurements (TDD)".
[23] 3GPP TS 51.010-1: " Mobile Station (MS) conformance specification; Part 1: Conformance specification".
[24] 3GPP TS 25.306: "UE Radio Access capabilities definition".
[25] ITU-T recommendation O.153: "Basic parameters for the measurement of error performance at bit rates below the primary rate".
[26] 3GPP TS 36.133: "Requirements for support of radio resource management"
[27] 3GPP TS 36.101: “User Equipment (UE) radio transmission and reception”
[28] 3GPP TS 36.508: "Technical Specification Group Radio Access Network; E-UTRA and EPC; Common test environments for User Equipment (UE)"
[29] 3GPP TS 36.133: "E-UTRA requirements for support of radio resource management".
[30] 3GPP TS 36.211: "Physical Channels and Modulation".
[31] 3GPP TS 36.331: "E-UTRA Radio Resource Control (RRC): protocol specification".
[32] 3GPP TS 36.101: "E-UTRA UE radio transmission and reception".
[33] 3GPP TS 36.521-3: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; Radio transmission and reception; Part 3: Radio Resource Management (RRM) conformance testing".
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
3 Definitions, abbreviations and equations
|
For the purposes of the present document, the definitions, symbols, abbreviations and equations used in the present document are listed in TR 21.905 [6] and TR 25.990 [7].
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
3.1 Definitions
|
For the purpose of the present document, the following definition applies:
Power Spectral Density: The units of Power Spectral Density (PSD) are extensively used in this document. PSD is a function of power versus frequency and when integrated across a given bandwidth, the function represents the mean power in such a bandwidth. When the mean power is normalised to (divided by) the chip-rate it represents the mean energy per chip. Some signals are directly defined in terms of energy per chip, (DPCH_Ec, Ec, and P-CCPCH_Ec) and others defined in terms of PSD (Io, Ioc, Ior and Îor). There also exist quantities that are a ratio of energy per chip to PSD (DPCH_Ec/Ior, Ec/Ior etc.). This is the common practice of relating energy magnitudes in communication systems.
It can be seen that if both energy magnitudes in the ratio are divided by time, the ratio is converted from an energy ratio to a power ratio, which is more useful from a measurement point of view. It follows that an energy per chip of X dBm/3,84 MHz (3,84 Mcps TDD option) or X dBm/1,281,28 MHz (1,281,28 Mcps TDD option) can be expressed as a mean power per chip of X dBm. Similarly, a signal PSD of Y dBm/3,84 MHz (3,84 Mcps TDD option) or Y dBm/1,281,28 MHz (1,281,28 Mcps TDD option) can be expressed as a signal power of Y dBm.
Maximum Output Power: This is a measure of the maximum power the UE can transmit (i.e. the actual power as would be measured assuming no measurement error) in a bandwidth of at least (1+ times the chip rate of the radio access mode. The period of measurement shall be a transmit timeslot excluding the guard period.
Mean Power: When applied to a CDMA modulated signal this is the power (transmitted or received) in a bandwidth of at least (1+ times the chip rate of the radio access mode. The period of measurement shall be a transmit timeslot excluding the guard period unless otherwise stated.
Output power: The mean power of the UE delivered to a load with resistance equal to the nominal load impedance of the transmitter.
RRC Filtered Mean Power: The mean power as measured through a root raised cosine filter with roll-off factor and a bandwidth equal to the chip rate of the radio access mode.
Nominal Maximum Output Power: This is the nominal power defined by the UE power class. The period of measurement shall be a transmit timeslot excluding the guard period.
Received Signal Code Power (RSCP): Given only signal power is received, the RRC filtered mean power of the received signal after despreading and combining.
Interference Signal Code Power (ISCP): Given only interference power is received, the RRC filtered mean power of the received signal after despreading to the code and combining. Equivalent to the RSCP value but now only interference is received instead of signal.
The following two definitions are applicable for LCR TDD multi-frequency operation.
Inter-frequency cell: In idle, CELL-FACH, CELL-PCH and URA-PCH state, inter-frequency cell is defined as the cell of which the primary frequency is different from the user’s current frequency. In CELL-DCH state, inter-frequency cell is defined as the cell of which the frequency to be measured in that cell is different from the operating frequency for single carrier operation or is different from the associated DPCH operating frequency for multi-carrier operation.
Intra-frequency cell: In idle, CELL-FACH, CELL-PCH and URA-PCH state, intra-frequency cell is defined as the cell of which the primary frequency is the same as the user’s current frequency. In CELL-DCH state, intra-frequency cell is defined as the cell of which the frequency to be measured in that cell is the same as the operating frequency for single carrier operation or is the same as the associated DPCH operating frequency for multi-carrier operation.
NOTE 1: The RRC filtered mean power of a perfectly modulated CDMA signal is 0.246 dB lower than the mean power of the same signal.
NOTE 2: The roll-off factor is defined in section 6.8.1 of [1].
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
3.2 Abbreviations
|
For the purpose of the present document, the following abbreviations apply.
ACLR Adjacent Channel Leakage power Ratio
ACS Adjacent Channel Selectivity
AFC Automatic Frequency Control
ATT Attenuator
CW Continuous wave (unmodulated signal)
DPCH Dedicated physical channel
DPCH_Ec Average energy per PN chip for DPCH
EVM Error Vector Magnitude
FFS For Further Study
Fuw Frequency of unwanted signal. This is specified in bracket in terms of an absolute frequency(s) or frequency offset from the assigned channel frequency.
HYB Hybrid
IBTS Interference signal power level at BTS in dBm, which is broadcasted on BCH
IMB Integrated Mobile Broadcast
Ioac The power spectral density of the adjacent frequency channel as measured at the UE antenna connector.
Ioc The power spectral density (integrated in a noise bandwidth equal to the chip rate and normalized to the chip rate) of a band limited white noise source (simulating interference from cells which are not defined in a test procedure) as measured at the UE antenna connector.
Ior The total transmit power spectral density (integrated in a bandwidth of (1+α) times the chip rate and normalized to the chip rate) of the downlink signal at the BS antenna connector
The received power spectral density (integrated in a bandwidth of (1+α) times the chip rate and normalized to the chip rate) of the downlink signal as measured at the UE antenna connector
Iowc Unwanted signal power level
OBW Occupied Bandwidth
OCNS Orthogonal Channel Noise Simulator, a mechanism used to simulate the users or control signals on the other orthogonal channels of a downlink.
PCDE Peak Code Domain Error
PPM Parts Per Million
PRBS Pseudo Random Bit Sequence
RRC Root-Raised Cosine
SCTD Space Code Transmit Diversity
SIR Signal to Interference ratio
SS System Simulator
TBD To Be Defined
TPC Transmit Power Control
TS Time Slot
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
3.3 Equations
|
For the purpose of the present document, the following additional equations apply:
The ratio of the average energy per PN chip of the DPCH to the total transmit power spectral density of the downlink at the BS antenna connector
The ratio of the sum of DPCH_Ec for one service in case of multicode to the total transmit power spectral density of the downlink at the BS antenna connector
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
4 Frequency bands and channel arrangement
| |
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
4.1 General
|
The information presented in this clause is based on the chip rates of 3,84 Mcps TDD Option,1,28 Mcps TDD Option and 7.68Mcps Option.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
4.2 Frequency bands
|
UTRA/TDD is designed to operate in the following bands;
a) 1 900 – 1 920 MHz: Uplink and downlink transmission
2 010 – 2 025 MHz Uplink and downlink transmission
b) 1 850 – 1 910 MHz: Uplink and downlink transmission
1 930 – 1 990 MHz: Uplink and downlink transmission
c) 1 910 – 1 930 MHz: Uplink and downlink transmission
d) 2 570 - 2 620 MHz: Uplink and downlink transmission
e) 2300—2400 MHz: Uplink and downlink transmission
f) 1880 - 1920 MHz: Uplink and downlink transmission
NOTE 1: Deployment in existing or other frequency bands is not precluded.
NOTE 2: In China, Band a only includes 2010 - 2025 MHz for 1.28 Mcps TDD option.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
4.3 TX–RX frequency separation
| |
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
4.3.1 3,84 Mcps TDD Option
|
No TX-RX frequency separation is required as Time Division Duplex (TDD) is employed. Each TDMA frame consists of 15 timeslots where each timeslot can be allocated to either transmit or receive.
The IMB option is only applicable for dedicated carrier operations in which all TDD slots of the radio frame are configured in the downlink direction
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
4.3.2 1,28 Mcps TDD Option
|
No TX-RX frequency separation is required as Time Division Duplex (TDD) is employed. Each subframe consists of 7 main timeslots where all main timeslots (at least the first one) before the single switching point are allocated DL and all main timeslots (at least the last one) after the single switching point are allocated UL.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
4.3.3 7,68 Mcps TDD Option
|
No TX-RX frequency separation is required as Time Division Duplex (TDD) is employed. Each TDMA frame consists of 15 timeslots where each timeslot can be allocated to either transmit or receive.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
4.4 Channel arrangement
| |
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
4.4.1 Channel spacing
| |
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
4.4.1.1 3,84 Mcps TDD Option
|
The nominal channel spacing is 5 MHz, but this can be adjusted to optimise performance in a particular deployment scenario.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
4.4.1.2 1,28 Mcps TDD Option
|
The nominal channel spacing is 1,6 MHz, but this can be adjusted to optimise performance in a particular deployment scenario.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
4.4.1.3 7,68 Mcps TDD Option
|
The nominal channel spacing is 10 MHz, but this can be adjusted to optimise performance in a particular deployment scenario.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
4.4.2 Channel raster
|
The channel raster is 200 kHz, which means that the carrier frequency must be a multiple of 200 kHz.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
4.4.3 Channel number
|
The carrier frequency is designated by the UTRA absolute radio frequency channel number (UARFCN). The value of the UARFCN in the IMT2000 band is defined as follows:
Nt = 5 * F
0,0 MHz £ F £ 3276,6 MHz
where F is the carrier frequency in MHz
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
4.4.4 UARFCN (3,84 Mcps TDD Option)
|
The following UARFCN range shall be supported for each band.
Table 4.4.1: UTRA Absolute Radio Frequency Channel Number
Frequency Band
Frequency Range
UARFCN Uplink and Downlink transmission
For operation in frequency band as defined in subclause 4.2 (a)
1900-1920 MHz
2010-2025 MHz
9512 to 9588
10062 to 10113
For operation in frequency band as defined in subclause 4.2 (b)
1850-1910 MHz
1930-1990 MHz
9262 to 9538
9662 to 9938
For operation in frequency band as defined in subclause 4.2 (c)
1910-1930 MHz
9562 to 9638
For operation in frequency band as defined in subclause 4.2 (d)
2570-2620 MHz
12862 to 13088
4.4.4A UARFCN (1.28 Mcps TDD Option)
The following UARFCN range shall be supported for each band.
Table 4.4.1A: UTRA Absolute Radio Frequency Channel Number
Frequency Band
Frequency Range
UARFCN Uplink and Downlink transmission
For operation in frequency band as defined in subclause 4.2 (a)
1900-1920 MHz
2010-2025 MHz
9504 to 9596
10054 to 10121
For operation in frequency band as defined in subclause 4.2 (b)
1850-1910 MHz
1930-1990 MHz
9254 to 9546
9654 to 9946
For operation in frequency band as defined in subclause 4.2 (c)
1910-1930 MHz
9554 to 9646
For operation in frequency band as defined in subclause 4.2 (d)
2570-2620 MHz
12854 to 13096
For operation in frequency band as defined in subclause 4.2 (e)
2300-2400 MHz
11504 to 11996
For operation in frequency band as defined in subclause 4.2 (f)
1880-1920 MHz
9404 to 9596
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
4.4.5 UARFCN (7,68 Mcps TDD Option)
|
The following UARFCN range shall be supported for each band.
Table 4.4.2: UTRA Absolute Radio Frequency Channel Number
Frequency Band
Frequency Range
UARFCN Uplink and Downlink transmission
Additional UARFCN Uplink and Downlink transmission
For operation in frequency band as defined in subclause 4.2 (a)
1900-1920 MHz
2010-2025 MHz
9512 to 9588
10062 to 10113
-
For operation in frequency band as defined in subclause 4.2 (b)
1850-1910 MHz
1930-1990 MHz
9262 to 9538
9662 to 9938
-
For operation in frequency band as defined in subclause 4.2 (c)
1910-1930 MHz
9562 to 9638
-
For operation in frequency band as defined in subclause 4.2 (d)
2570-2620 MHz
12874 to 13076
-
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5 Transmitter Characteristics
| |
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.1 General
|
Transmitting performance test of the UE is implemented during communicating with the SS via air interface. The procedure is uses normal call protocol until the UE is communicating on traffic channel basically. (Refer to TS 34.108 [3] Common Test Environments for User Equipment (UE) Conformance Testing) On the traffic channel, the UE provides special function for testing that is called Logical Test Interface and the UE is tested using this function. (Refer to TS 34.109 [4] Logical Test Interface; Special conformance testing functions).
Unless detailed the transmitter characteristic are specified at the antenna connector of the UE. For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed. Transmitter characteristics for UE(s) with multiple antennas/antenna connectors are for further study.
The UE antenna performance has a significant impact on system performance, and minimum requirements on the antenna efficiency are therefore intended to be included in future versions of the present document. It is recognized that different requirements and test methods are likely to be required for the different types of UE.
The common RF test conditions are defined in annex E, and each test conditions in this Clause should refer annex E. Individual test conditions are defined in the paragraph of each test.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.2 User Equipment maximum output power
| |
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.2.1 Definition and applicability
|
The nominal maximum output power and its tolerance are defined according to the Power Class of the UE.
The requirements in this test apply to all UTRA – TDD- UEs
Notes copied from TS 25.102 clause 6.2.1:
NOTE 1: For multi-code operation the nominal maximum output power will be reduced by the difference of peak to average ratio between single and multi-code transmission.
NOTE 2: The tolerance allowed for the nominal maximum power applies even at the multi-code transmission mode
NOTE 3: For UE using directive antennas for transmission, a class dependent limit will be placed on the maximum EIRP (Equivalent Isotropic Radiated Power).
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.2.2 Minimum Requirements
| |
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.2.2.1 3.84 Mcps TDD option
|
The error of the UE maximum output power shall not exceed the tolerance shown in tables 5.2.2 1.a and b for single and multi-code for 3.84Mcps TDD option.
Table 5.2.2.1.a: Maximum Output Power single code
Power Class
Nominal maximum output power
Tolerance
1
+30 dBm
+1dB/-3dB
2
+24 dBm
+1dB/-3dB
3
+21 dBm
+2dB/-2dB
4
+10 dBm
+4dB/-4dB
Table 5.2.2.1.b: Maximum Output Power multi code
Power Class
Nominal maximum output power
Tolerance
1
+27 dBm (note)
+1dB/-3dB
2
21 dBm (note)
+1dB/-3dB
3
18 dBm (note)
+2dB/-2dB
4
+7 dBm (note)
+4dB/-4dB
NOTE: These figures are not mentioned in 25.102. Instead there is a note, saying:
"For multi-code operation the maximum output power will be reduced by the difference of peak to average ratio between single and multi-code transmission."
The figures are calculated from maximum output power single code (table 5.2.2.1.a) and UL multicode reference measurement channel (12,2 kbit/s) (annex C.2.2.1 for the 3,84 TDD Option) containing two code signals with equal level.
The normative reference for this requirement is TS 25.102 [1] clause 6.2.1.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.2.2.2 1.28 Mcps TDD option
|
The error of the UE maximum output power shall not exceed the tolerance shown in tables 5.2.2 2.a and b for single and multi-code for 1.28Mcps TDD option.
Table 5.2.2.2.a: Maximum Output Power single code
Power Class
Nominal maximum output power
Tolerance
1
+33 dBm
+1dB/-3dB
2
+24 dBm
+1dB/-3dB
3
+21 dBm
+2dB/-2dB
4
+27 dBm
+1dB/-3dB
Table 5.2.2.2.b: Maximum Output Power multi code
Power Class
Nominal maximum output power
Tolerance
1
+30 dBm (note)
+1dB/-3dB
2
22 dBm (note)
+1dB/-3dB
3
18 dBm (note)
+2dB/-2dB
4
+24 dBm (note)
+1dB/-3dB
NOTE: These figures are not mentioned in 25.102. Instead there is a note, saying:
"For multi-code operation the maximum output power will be reduced by the difference of peak to average ratio between single and multi-code transmission."
The figures are calculated from maximum output power single code (table 5.2.2.a) and UL multicode reference measurement channel (12,2 kbit/s) (annex C.2.2.2 for the 1,28 Mcps TDD Option) containing two code signals with equal level.
The normative reference for this requirement is TS 25.102 [1] clause 6.2.1.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.2.2.3 7.68 Mcps TDD option
|
The error of the UE maximum output power shall not exceed the tolerance shown in tables 5.2.2 1.a and b for single and multi-code for 7.68Mcps TDD option.
Table 5.2.2.1.a: Maximum Output Power single code
Power Class
Nominal maximum output power
Tolerance
1
+30 dBm
+1dB/-3dB
2
+24 dBm
+1dB/-3dB
3
+21 dBm
+2dB/-2dB
4
+10 dBm
+4dB/-4dB
Table 5.2.2.1.b: Maximum Output Power multi code
Power Class
Nominal maximum output power
Tolerance
1
+27 dBm (note)
+1dB/-3dB
2
21 dBm (note)
+1dB/-3dB
3
18 dBm (note)
+2dB/-2dB
4
+7 dBm (note)
+4dB/-4dB
NOTE: These figures are not mentioned in 25.102. Instead there is a note, saying:
"For multi-code operation the maximum output power will be reduced by the difference of peak to average ratio between single and multi-code transmission."
The figures are calculated from maximum output power single code (table 5.2.2.1.a) and UL multicode reference measurement channel (12,2 kbit/s) (annex C.2.2.3 for the 7.68 TDD Option) containing two code signals with equal level.
The normative reference for this requirement is TS 25.102 [1] clause 6.2.1.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.2.3 Test purpose
|
For the following reasons:
Limit interference.
Verify that the maximum output power is achievable.
It is the purpose of the test to verify that the UE's maximum output power is within its tolerance limits under all environmental conditions.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.2.4 Method of test
| |
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.2.4.1 Initial conditions
|
Test environment: normal, TL/VL, TL/VH, TH/VL, TH/VH; see clauses G.2.1 and G.2.2.
Frequencies to be tested: low range, mid range, high range; see clause G.2.4.
1) Connect the SS to the UE antenna connector as shown in figure A.1.
2) Calls are set up according to the Generic call setup procedure using parameters as specified in tables 5.2.4.1.1a and b for the 3,84 Mcps TDD Option and in tables 5.2.4.1.2a and b for the 1,28 Mcps TDD Option, respectively.
3) Enter the UE into loopback test mode and start the loopback test.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.2.4.1.1 3,84 Mcps TDD Option
|
Table 5.2.4.1.1a: Test parameters for Maximum Output Power single code (3,84 Mcps TDD Option)
Parameter
Value/description
UL Reference measurement channel
12,2 kbps, according to annex C.2.1.1
Uplink Power Control
SS level and signalling values such that UE transmits maximum power.
Data content
real life (sufficient irregular)
Table 5.2.4.1.1b: Test parameters for Maximum Output Power multicode (3,84 Mcps TDD Option)
Parameter
Value/description
Reference measurement channel
Multicode 12,2 kbps, according to annex C.2.2.1
Uplink Power Control
SS level and signalling values such that UE transmits maximum power
Data content
real life (sufficient irregular)
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.2.4.1.2 1,28 Mcps TDD Option
|
Table 5.2.4.1.2a: Test parameters for Maximum Output Power single code (1,28 Mcps TDD Option)
Parameter
Value/description
UL Reference measurement channel
12,2 kbps, according to annex C.2.1.2.
Uplink Power Control
SS level and signalling values such that UE transmits maximum power.
Data content
real life (sufficient irregular)
Table 5.2.4.1.2b: Test parameters for Maximum Output Power multicode (1,28 Mcps TDD Option)
Parameter
Value/description
Reference measurement channel
Multicode 12,2 kbps, according to annex C.2.2.2
Uplink Power Control
SS level and signalling values such that UE transmits maximum power
Data content
real life (sufficient irregular)
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.2.4.1.3 7,68 Mcps TDD Option
|
Table 5.2.4.1.3a: Test parameters for Maximum Output Power single code (7,68 Mcps TDD Option)
Parameter
Value/description
UL Reference measurement channel
12,2 kbps, according to annex C.2.1.3
Uplink Power Control
SS level and signalling values such that UE transmits maximum power.
Data content
real life (sufficient irregular)
Table 5.2.4.1.3b: Test parameters for Maximum Output Power multicode (7,68 Mcps TDD Option)
Parameter
Value/description
Reference measurement channel
Multicode 12,2 kbps, according to annex C.2.2.3
Uplink Power Control
SS level and signalling values such that UE transmits maximum power
Data content
real life (sufficient irregular)
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.2.4.2 Procedure
|
1) Measure the mean power of the UE output signal.
2) Run step 1) for RF channels Low / Mid / High.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.2.5 Test Requirements
| |
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.2.5.1 3,84 Mcps TDD Option
|
The output power, measured in step 2) of clause 5.2.4.2, shall not exceed the prescribed tolerance in table 5.2.5 a and b.
Table 5.2.5.1.a: Maximum Output Power single code
Power Class
Nominal maximum output power
Tolerance
1
+30 dBm
+1,7 dB / -3,7 dB
2
+24 dBm
+1,7 dB / -3,7dB
3
+21 dBm
+2,7 dB / -2,7dB
4
+10 dBm
+4,7 dB /-4,7dB
Table 5.2.5.1.b: Maximum Output Power multi code
Power Class
Nominal maximum output power
Tolerance
1
27 dBm
+1,7 dB / -3,7 dB
2
21 dBm
+1,7dB / -3,7 dB
3
18 dBm
+2,7dB / -2,7 dB
4
7 dBm
+4,7 dB / -4,7 dB
NOTE 1: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in annex F clause F.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex F clause F.4.
NOTE 2: Concerning multicode transmission this test applies only for UE power classes 2 and 3. It is intended, that additional test requirements for UE power classes 1 and 4 in this case are part of a later version of the present document.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.2.5.2 1.28 Mcps TDD Option
|
The output power, measured in step 2) of clause 5.2.4.2, shall not exceed the prescribed tolerance in table 5.2.5.2 a and b.
Table 5.2.5.2.a: Maximum Output Power single code
Power Class
Nominal maximum output power
Tolerance
1
+33dBm
+1,7 dB / -3,7 dB
2
+24 dBm
+1,7 dB / -3,7dB
3
+21 dBm
+2,7 dB / -2,7dB
4
+27 dBm
+1,7 dB / -3,7 dB
Table 5.2.5.2.b: Maximum Output Power multi code
Power Class
Nominal maximum output power
Tolerance
1
30 dBm
+1,7 dB / -3,7 dB
2
22 dBm
+1,7dB / -3,7 dB
3
18 dBm
+2,7dB / -2,7 dB
4
24 dBm
+1,7 dB / -3,7 dB
NOTE 1: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in annex F clause F.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex F clause F.4.
NOTE 2: Concerning multicode transmission this test applies only for UE power classes 2 and 3. It is intended, that additional test requirements for UE power classes 1 and 4 in this case are part of a later version of the present document.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.2.5.3 7.68 Mcps TDD Option
|
The output power, measured in step 2) of clause 5.2.4.2, shall not exceed the prescribed tolerance in table 5.2.5.3 a and b.
Table 5.2.5.3.a: Maximum Output Power single code
Power Class
Nominal maximum output power
Tolerance
1
+33dBm
+1,7 dB / -3,7 dB
2
+24 dBm
+1,7 dB / -3,7dB
3
+21 dBm
+2,7 dB / -2,7dB
4
+27 dBm
+1,7 dB / -3,7 dB
Table 5.2.5.3.b: Maximum Output Power multi code
Power Class
Nominal maximum output power
Tolerance
1
30 dBm
+1,7 dB / -3,7 dB
2
21 dBm
+1,7dB / -3,7 dB
3
18 dBm
+2,7dB / -2,7 dB
4
24 dBm
+1,7 dB / -3,7 dB
NOTE 1: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in annex F clause F.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex F clause F.4.
NOTE 2: Concerning multicode transmission this test applies only for UE power classes 2 and 3. It is intended, that additional test requirements for UE power classes 1 and 4 in this case are part of a later version of the present document.
5.2A User Equipment maximum output power with E-DCH
5.2A.1 Definition and applicability
The maximum output power with E-DCH and its tolerance are defined according to the UE Maximum Power Reduction (MPR) for the nominal maximum output power.
The requirements and this test apply for Release 7 and later releases to all types of UTRA for the TDD UE that support HSUPA.
5.2A.2 Minimum Requirements
5.2A.2.1 3.84 Mcps TDD option
[FFS]
5.2A.2.2 1.28 Mcps TDD option
The UE Maximum Power Reduction (MPR) for the nominal maximum output power shall be within the value and tolerance specified in table 5.2A.2.2.a
Table 5.2A.2.2.a: UE maximum output power with E-DCH
UE transmit channel configuration
CM (dB)
MPR (dB)
E-DCH and E-UCCH
0 CM 1.5
CM
Where Cubic Metric (CM) is based on the UE transmit channel configuration and is given by
CM = [20 * log10 ((v_norm 3) rms) - 20 * log10 ((v_norm_ref 3) rms)] / k
Where
- v_norm is the normalized voltage waveform of the input signal
- v_norm_ref is the normalized voltage waveform of the reference signal (12.2 kbps AMR Speech)
- k is 1.94
- 20 * log10 ((v_norm_ref 3) rms) = 1.22 dB
The normative reference for this requirement is TS 25.102 clause 6.2.2.
5.2A.2.3 7.68 Mcps TDD option
[FFS]
5.2A.3 Test purpose
To verify that the error of the UE maximum output power with E-DCH does not exceed the range prescribed by the maximum output power and tolerance in table 5.2A.5.2.a.
An excess maximum output power may interfere with other channels or other systems. A small maximum output power decreases the coverage area.
5.2A.4 Method of test
5.2A.4.1 Initial conditions
Test environment: normal, TL/VL, TL/VH, TH/VL, TH/VH; see clauses G.2.1 and G.2.2.
Frequencies to be tested: low range, mid range, high range; see clause G.2.4.
1) Connect the SS (node B emulator) to the UE antenna connector as shown in figure A.1.
2) The Fixed Reference Channels (FRC 3, 16QAM) are specified C.6.1.2.3.
3) An E-DCH call is set up according to TS 34.108 [3] 7.3.9
4) Enter the UE into loopback test mode 1 looping back both the 12.2kbps RMC and HSDPA to E-DCH, and start the loopback test.
See TS 34.109 [4] clauses 5.3.2.3 and 5.3.2.6 for details regarding loopback test mode for HSDPA and E-DCH.
5.2A.4.1.1 3,84 Mcps TDD Option
[FFS]
5.2A.4.1.2 1,28 Mcps TDD Option
Table 5.2A.4.1.2a: Test parameters for Maximum Output Power single code (1,28 Mcps TDD Option)
Parameter
Value/description
UL Reference measurement channel
12,2 kbps, according to annex C.2.1.2.
Uplink Power Control
SS level and signalling values such that UE transmits maximum power.
Data content
real life (sufficient irregular)
Table 5.2A.4.1.2b: Test parameters for Maximum Output Power multicode (1,28 Mcps TDD Option)
Parameter
Value/description
Reference measurement channel
Multicode 12,2 kbps, according to annex C.2.2.2
Uplink Power Control
SS level and signalling values such that UE transmits maximum power
Data content
real life (sufficient irregular)
5.2 A.4.1.3 7,68 Mcps TDD Option
[FFS]
5.2A.4.2 Procedure
1) The SS starts transmitting and the UE loops the received data back on E-DCH.
2) Set the UE power to be at least 7.5dB lower than the maximum output power. Wait 150ms.
3) Send power control bits to give one TPC_cmd = +1 command to the UE.
4) The SS checks the received E-TFCI for 150 ms. If UE does not send any decreased E-TFCI within the 150ms then go back to step (3) otherwise proceed to step 5).
5) Send power control bits to give one TPC_cmd = -1 command to the UE and wait 150ms.
6) The SS checks the received E-TFCI for 150 ms. If UE sends any decreased E-TFCI within the 150ms, then send new power control bits to give another TPC_cmd = -1 command to the UE and wait 150ms.
7) Confirm that the E-TFCI transmitted by the UE is equal to the target E-TFCI = 53. If the E-TFCI transmitted by the UE is not equal to the target E-TFCI, then fail the UE.
8) Measure the mean power of the UE. The mean power shall be averaged over at least one timeslot.
5.2A.5 Test requirements
5.2A.5.1 3.84 Mcps TDD Option
[FFS]
5.2A.5.2 1.28 Mcps TDD Option
The maximum output power with E-DCH, derived in step 7), shall not exceed the range prescribed by the maximum output power and tolerance in table 5.2A.5.2.a.
Table 5.2A.5.2.a: Maximum Output Powers with E-DCH for test
UE transmit channel configuration
Power Class1
Nominal maximum output power
Tolerance
E-DCH and E-UCCH
FFS
FFS
UE transmit channel configuration
Power Class2
Nominal maximum output power
Tolerance
E-DCH and E-UCCH
22.5dBm
+3.2dB / -5.2dB
UE transmit channel configuration
Power Class3
Nominal maximum output power
Tolerance
E-DCH and E-UCCH
FFS
FFS
UE transmit channel configuration
Power Class4
Nominal maximum output power
Tolerance
E-DCH and E-UCCH
FFS
FFS
NOTE 1: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in annex F clause F.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex F clause F.4.
NOTE2: The test procedure will result in a power slightly below the maximum, and therefore the lower limits in Table 5.2A.5.2.a are made lower by 1.5 dB.
5.2A.5.3 7.68 Mcps TDD Option
[FFS]
5.2B User Equipment maximum output power with HS-SICH and DPCH
5.2B.1 Definition and applicability
The maximum output power with HS-SICH and DPCH and its tolerance are defined according to the UE Maximum Power Reduction (MPR) for the nominal maximum output power.
The requirements and this test apply for Release 5 and later releases to all types of UTRA for the TDD UE that support HSDPA.
5.2B.2 Minimum Requirements
5.2B.2.1 3.84 Mcps TDD option
[FFS]
5.2B2.2 1.28 Mcps TDD option
The UE Maximum Power Reduction (MPR) for the nominal maximum output power shall be within the value and tolerance specified in table 5.2B.2.2.b
Table 5.2B.2.2.b: UE maximum output power with HS-SICH and DPCH
UE transmit channel configuration
CM (dB)
MPR (dB)
HS-SICH and DPCH
0 CM 2.5
CM
Where Cubic Metric (CM) is based on the UE transmit channel configuration and is given by
CM = [20 * log10 ((v_norm 3) rms) - 20 * log10 ((v_norm_ref 3) rms)] / k
Where
- v_norm is the normalized voltage waveform of the input signal
- v_norm_ref is the normalized voltage waveform of the reference signal (12.2 kbps AMR Speech)
- k is 1.68
- 20 * log10 ((v_norm_ref 3) rms) = 1.22 dB
The normative reference for this requirement is TS 25.102 clause 6.2.2.
5.2B.2.3 7.68 Mcps TDD option
[FFS]
5.2B.3 Test purpose
To verify that the error of the UE maximum output power with HS-SICH and DPCH does not exceed the range prescribed by the maximum output power and tolerance in table 5.2B.2.2b.
An excess maximum output power may interfere with other channels or other systems. A small maximum output power decreases the coverage area.
5.2B.4 Method of test
5.2B.4.1 Initial conditions
Test environment: normal, TL/VL, TL/VH, TH/VL, TH/VH; see clauses G.2.1 and G.2.2.
Frequencies to be tested: low range, mid range, high range; see clause G.2.4.
1) Connect the SS (node B emulator) to the UE antenna connector as shown in figure A.1.
2) The Reference Measurement Channels are specified C.2.2.2a.
3) An HSDPA call is set up according to TS 34.108 [3] 7.3.6
4) Enter the UE into loopback test mode in the presence of HSDPA and start the loopback test.
See TS 34.108 [3] and TS 34.109 [4] for details regarding loopback test mode for HSDPA
5.2B.4.2 Procedure
1) The SS starts transmitting HSDPA data.
2) Set SS-level and signalling values such that the power level of both DPCH and HS-SICH are between 12.5-14dBm
3) Send power control bits continuously to give TPC_cmd = +1 command to DPCH and HS-SICH simultaneously.
4) Measure the mean power of the UE. The mean power shall be averaged over at least one timeslot.
5.2B.5 Test requirements
5.2B.5.1 3.84 Mcps TDD Option
[FFS]
5.2B.5.2 1.28 Mcps TDD Option
The maximum output power with HS-SICH and DPCH, derived in step 7), shall not exceed the range prescribed by the maximum output power and tolerance in table 5.2B.5.2b.
Table 5.2A.5.2b.: Maximum Output Powers with HS-SICH and DPCH for test
UE transmit channel configuration
Power Class1
Nominal maximum output power
Tolerance
For some combinations of; HS-SICH and DPCH
FFS
FFS
UE transmit channel configuration
Power Class2
Nominal maximum output power
Tolerance
For some combinations of; HS-SICH and DPCH
21.5dBm
+4.2 dB / -3.7dB
UE transmit channel configuration
Power Class3
Nominal maximum output power
Tolerance
For some combinations of; HS-SICH and DPCH
FFS
FFS
UE transmit channel configuration
Power Class4
Nominal maximum output power
Tolerance
For some combinations of; HS-SICH and DPCH
FFS
FFS
NOTE 1: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in annex F clause F.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex F clause F.4.
5.2B.5.3 7.68 Mcps TDD Option
[FFS]
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.3 UE frequency stability
| |
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.3.1 Definition and applicability
|
The frequency stability is the difference of the modulated carrier frequency between the RF transmission from the UE and the RF transmission from the BS. The UE shall use the same frequency source for both RF frequency generation and chip clocking.
The requirements of this test apply to all types of UTRA- UE.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.3.2 Minimum Requirements
|
The UE frequency stability, observed over a period of one timeslot, shall be within ±0,1 ppm compared to signals received from the BS.
The normative reference for this requirement is TS 25.102 [1] clause 6.3.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.3.3 Test purpose
|
Reliable frequency stability of the UE's transmitter in certain tolerance limits is prerequisite for connectivity.
This test stresses the ability of the UE's receiver to derive correct frequency information from the received signal for the transmitter.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.3.4 Method of test
| |
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.3.4.1 Initial conditions
|
Test environment: normal, TL/VL, TL/VH, TH/VL, TH/VH, vibration; see clauses G.2.1, G.2.2 and G.2.3.
Frequencies to be tested: low range, mid range, high range; see clause G.2.4.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.3.4.1.1 3,84 Mcps TDD Option
|
1) Connect the SS to the UE antenna connector as shown in figure A.1.
2) A call is set up according to the Generic call setup procedure using parameters as specified in table 5.3.4.1.1.
3) Enter the UE into loopback test mode and start the loopback test.
Table 5.3.4.1.1: Test parameters for Frequency Stability (3,84 Mcps TDD Option)
Parameter
Value/description
SS level (Ior)
–105 dBm / 3,84 MHz
(reference sensitivity)
UL reference measurement channel
12,2 kbps according to annex C.2.1.1.
Data content
real life (sufficient irregular)
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.3.4.1.2 1,28 Mcps TDD Option
|
1) Connect the SS to the UE antenna connector as shown in figure A.1.
2) A call is set up according to the Generic call setup procedure using parameters as specified in table 5.3.4.1.2.
3) Enter the UE into loopback test mode and start the loopback test.
Table 5.3.4.1.2: Test parameters for Frequency Stability (1,28 Mcps TDD Option)
Parameter
Value/description
SS level (Ior)
–108 dBm / 1,28 MHz
(reference sensitivity)
UL reference measurement channel
12,2 kbps according to annex C.2.1.2
Data content
real life (sufficient irregular)
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.3.4.1.3 7,68 Mcps TDD Option
|
1) Connect the SS to the UE antenna connector as shown in figure A.1.
2) A call is set up according to the Generic call setup procedure using parameters as specified in table 5.3.4.1.3.
3) Enter the UE into loopback test mode and start the loopback test.
Table 5.3.4.1.3: Test parameters for Frequency Stability (7,68 Mcps TDD Option)
Parameter
Value/description
SS level (Ior)
–102 dBm / 7,68 MHz
(reference sensitivity)
UL reference measurement channel
12,2 kbps according to annex C.2.1.3.
Data content
real life (sufficient irregular)
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.3.4.2 Procedure
|
1) Measure the frequency error delta f across the TS according to annex B.
2) Repeat step 1) for 200 bursts (time slots).
3) Run Step 1) and 2) for RF channels Low /Mid/ High.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.3.5 Test Requirements
|
For all measured bursts (time slots), the frequency error, derived in clause 5.3.4.2, shall not exceed ±(0,1 ppm + 10 Hz).
NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in annex F clause F.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex F clause F.4
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4 Output Power Dynamics
|
Power control is used to limit the interference level.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1 Uplink power control
|
Uplink power control is the ability of the UE transmitter to sets its output power in accordance with measured downlink path loss, values determined by higher layer signalling and path loss weighting parameter a as defined in TS 25.331 [9]. The output power is defined as the RRC filtered mean power of the transmit timeslot.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.1 Initial accuracy (3,84 Mcps TDD Option)
| |
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.1.1 Definition and applicability
|
Initial Uplink power control is the ability of the UE transmitter to sets its output power in accordance with measured downlink path loss, and signalling values: IBTS and Constant value, received from the BCH and applicable for the PRACH.
The requirements and this test apply to all types of UTRA - UEs.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.1.2 Minimum requirements
|
The UE power control, initial accuracy, is given in table 5.4.1.1.2.
Table 5.4.1.1.2: Initial uplink power control tolerance (3,84 Mcps TDD Option)
Normal conditions
±9 dB
Extreme conditions
±12 dB
The reference for this requirement is TS 25.102 [1] clause 6.4.1.1.1.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.1.3 Test purpose
|
The power of the received signal at the UE and the BCH information control the power of the transmitted UE signal with the target to transmit at lowest power, acceptable for proper communication.
The test stresses the ability of the receiver to measure the received power over the receiver dynamic range and to derive from this correct transmitter-power.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.1.4 Method of test
| |
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.1.4.1 Initial conditions
|
Test environment: normal, TL/VL, TL/VH, TH/VL, TH/VH; see clauses G.2.1 and G.2.2.
Frequencies to be tested: low range, mid range, high range; see clause G.2.4.
Connect the SS to the MS antenna connector as shown in figure A.1.
A call is set up according to the generic call setup procedure [3] using parameters as specified in table 5.4.1.1.4. The RACH procedure within the call setup is used for the test.
Table 5.4.1.1.4: Test parameters for uplink Power Control (3,84 Mcps TDD Option)
RX-Upper dynamic end
RX-middle
RX-Sensitivity level
SS transmit power
-25 dBm/3,84 MHz
-65 dBm/3,84 MHz
-105 dBm/3,84 MHz
Broadcasted transmit- power PCCPCH
35 dBm
35 dBm
24 dBm
Simulated path loss =
Broadcasted TX – SS TX Power
60 dB
100 dB
129 dB
I BTS (UL interference)
-75 dBm
-100 dBm
-110 dBm
Constant value
-10 dB
-10 dB
-10 dB
Nominal expected UE TX power
-25 dBm
-10 dBm
+9 dBm (note 2)
NOTE 1: While the SS transmit power shall cover the UE receiver input dynamic range, the logical parameters: broadcasted transmit power, IBTS, and RACH constant value are chosen to achieve a UE TX power, located within the TX output power dynamic range of a class 3 UE.
NOTE 2: Nominal TX output power 9 dBm allows to check the uplink power control algorithm within the entire tolerance range (9 dBm +-12 dB: 9 dBm +12 dB =21 dBm = max power class 3).
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.1.4.2 Procedure
|
1) Set the SS transmit power according to table 5.4.1.1.4.
2) Measure the RACH output power of the UE according to annex B.
3) Repeat the test for all SS transmit powers and parameters in table 5.4.1.1.4.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.1.5 Test requirements
|
The deviation with respect to the nominal expected UE TX power (table 5.4.1.1.2), derived in step 2, shall not exceed the prescribed tolerance in table 5.4.1.1.5.
Table 5.4.1.1.5: Test parameters for uplink Power Control
Expected UE TX power, normal conditions
-25 dBm ±10 dB
-10 dBm±10 dB
+9 dBm ±10 dB
Expected UE TX power, extreme conditions
-25 dBm ±13 dB
-10 dBm±13 dB
+9 dBm ±13 dB
NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in annex F clause F.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex F clause F.4.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.2 Differential accuracy, controlled input (3,84 Mcps TDD Option)
| |
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.2.1 Definition and applicability
|
Uplink power control, differential accuracy, is the ability of the UE transmitter to sets its output power in accordance with measured downlink path loss, and the signalling values: I BTS, SIR Target, Constant Value, received from higher layers and applicable for the DPCH.
Specifically, the uplink power control, differential accuracy, controlled input, is defined as the error in the UE transmitter power step as a result of a step in SIRTARGET, IBTS or DPCH Constant Value when the path loss weighting parameter a=0.
The requirements of this test apply to all types of UTRA -UE.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.2.2 Minimum requirements
|
The step in SIRTARGET shall be rounded to the closest integer dB value. The power control error resulting from a change in SIRTARGET, IBTS or DPCH Constant Value shall not exceed the values in table 5.4.1.2.2.
Table 5.4.1.2.2: Transmitter power step tolerance as a result of control power step
(3,84 Mcps TDD Option)
DSIRTARGET [dB]
Transmitter power step tolerance [dB]
DSIRTARGET £ 1
± 0,5
1 < DSIRTARGET £ 2
± 1
2 < DSIRTARGET £ 3
± 1,5
3 < DSIRTARGET £ 10
± 2
10 < DSIRTARGET £ 20
± 4
20 < DSIRTARGET £ 30
± 6
30 < DSIRTARGET
± 9 (note)
NOTE: Value is given for normal conditions. For extreme conditions value is ±12.
The reference for this requirement is TS 25.102 [1] clause 6.4.1.1.2.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.2.3 Test purpose
|
It is verified if the UE sets correct uplink power steps in response to steps in the signalling value SIR Target and DPCH Constant Value, signalled via the downlink to the UE under the following conditions: keeping the other signalling parameters constant and deactivating any influence due to varying pathloss.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.2.4 Method of test
| |
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.2.4.1 Initial conditions
|
Test environment: normal; see clauses G.2.1 and G.2.2.
Frequencies to be tested: mid range; see clause G.2.4.
1) Connect the SS to the MS antenna connector as shown in figure A.1.
2) A call is set up according to the generic call setup procedure using parameters as specified in table 5.4.1.2.4.
Table 5.4.1.2.4 : Test parameters for Uplink Power Control, Differential Accuracy,
Controlled Input (3,84 Mcps TDD Option)
Parameter
Value/description
UL reference measurement channel
12,2 kbps according to annex C clause C.2.1.1
BS Transmit to UE Transmit delay
7 TSs--> a=0
SS Transmit power
-65 dBm
Reference transmit power broadcast on BCH
35 dBm
IBTS
-100
Constant value
-10
Data content
real life
(sufficient irregular)
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.2.4.2 Procedure
|
Using a combination of SIR Target and DPCH constant value signalled in the downlink, cover the UE-transmitter dynamic range by commanding the UEs power with the signalling value SIR Target in a step resolution (positive and negative direction) of:
1 dB approx. 68 steps up and 68 steps down
2 dB approx. 34 steps up and 34 steps down
3 dB approx. 22 steps up and 22 steps down
10 dB approx. 7 steps up and 7 steps down
20 dB approx. 3 steps up and 3 steps down
30 dB approx. 2 step up and 2 step down
maximum step size 1 step up and 1 step down
Measure the power according to annex B.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.2.5 Test requirements
|
For the UE output power laying between
Max Power minus tolerance and Min Power
the step response shall not exceed the prescribed tolerance in table 5.4.1.2.5.
Table 5.4.1.2.5: Transmitter power step tolerance as a result of control power step
DSIRTARGET [dB]
Transmitter power step tolerance [dB]
DSIRTARGET £ 1
± 0,6
1 < DSIRTARGET £ 2
± 1,15
2 < DSIRTARGET £ 3
± 1,7
3 < DSIRTARGET £ 10
± 2,5
10 < DSIRTARGET £ 20
± 4,7
20 < DSIRTARGET £ 30
± 6,7
30 < DSIRTARGET
± 10
NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in annex F clause F.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in annex F clause F.4.
5.4.1.2A Differential accuracy, controlled input
This is not tested.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.3 Open loop power control (1,28 Mcps TDD Option)
| |
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.3.1 Definition and applicability
|
Open loop power control is the ability of the UE transmitter to sets its output power to a specific value. The open loop power control tolerance is given in table 5.4.1.3.2.
The requirements and this test apply to all types of 1.28 Mcps TDD UE.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.3.2 Minimum requirements
|
The UE open loop power is defined as the average power in a timeslot or ON power duration, whichever is available, and they are measured with a filter that has a Root-Raised Cosine (RRC) filter response with a roll off and a bandwidth equal to the chip rate of 1,28 Mcps. The open loop power control tolerance is given in table 5.4.1.3.2.
Table 5.4.1.3.2: Open loop power control tolerance (1,28 Mcps TDD Option)
Normal conditions
±9 dB
Extreme conditions
±12 dB
The reference for this requirement is TS 25.102 [1] clause 6.4.1.2.1.1.
5.4.1.3.3 Test purpose
The power of the received signal and the BCCH information control the power of the transmitted signal with the target to transmit at lowest power acceptable for proper communication.
The test stresses the ability of the receiver to measure the received power correctly over the receiver dynamic range.
The test purpose is to verify that the UE open loop power control tolerance does not exceed the described value shown in table 5.4.1.3.2.
An excess error of the open loop power control decreases the system capacity.
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.3.4 Method of test
| |
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.3.4.1 Initial conditions
|
Test environment: normal, TL/VL, TL/VH, TH/VL, TH/VH; see clauses G.2.1 and G.2.2.
Frequencies to be tested: low range, mid range, high range; see clause G.2.4.
1) Connect the SS to the UE antenna connector as shown in figure A.1.
2) A call is set up according to the Generic call setup procedure, and RF parameters are set up according to table 5.4.1.3.4a. The transmit power level by a UE on the UpPTS is measured. The network signals on BCH a power increment that is applied only for the access procedure. At each new transmission of a UpPTS burst during the access procedure, the transmit power level can be increased by this power increment. According to the test purpose this power increment is set to zero.
See TS 34.108 [3] for details regarding generic call setup procedure.
Table 5.4.1.3.4a: Test parameters for Open Loop Power Control (UE) (1,28 Mcps TDD Option)
Parameter
Level / Status
Unit
Îor
See table 5.4.1.3.4b
dBm / 1,28 MHz
Table 5.4.1.3.4b: Test parameters for Open Loop Power Control (SS) (1,28 Mcps TDD Option) 1)
Parameter
RX Upper dynamic end
RX-middle
RX-Sensitivity level
SS transmit power Îor
-25 dBm / 1,28 MHz
- 66 dBm / 1,28 MHz
- 108 dBm / 1,28 MHz 3)
broadcasted Primary CCPCH transmit power
on BCH
+35 dBm
+24 dBm
+11 dBm
Simulated path loss = broadcasted TX – SS TX power
+60 dB
+90 dB
+119 dB
PRXUpPCHdes
-85 dBm
-100 dBm
-110 dBm
Pwrramp (Power Ramping Step)
0 dB
0 dB
0 dB
I (Max SYNC_UL Transmissions)
1
1
1
Expected nominal UE TX power 5)
-25 dBm
-10 dBm
+9 dBm 2)
Table 5.4.1.3.4c: Settings for the serving cell
Parameter
Unit
Cell 1
Cell type
Serving cell
Qrxlevmin
dBm
-115
UE_TXPWR_MAX_RACH
dBm
21
NOTE 1: While the SS transmit power shall cover the receiver input dynamic range, the logical parameters: broadcasted TX power, Desired UpPCH RX power at the BS receiver and Power Ramp step are chosen to achieve a UE TX power, located within the TX output power dynamic range of a class 3 UE.
NOTE 2: Nominal TX output power 9 dBm allows checking the open loop power algorithm within the entire tolerance range (9 dBm ± 12 dB; 9 dBm + 12 dB = 21 dBm = max power class 3)
NOTE 3: The reference for this requirement is TS 25.102 [1] clause 7.3.1.2.
NOTE 4: This test applies only for max UE power classes 3. It is intended, that additional test requirements for UE power class 4 are part of a later release.
NOTE 5: The Expected nominal UE TX power is calculated by using the equation in the clause 8.5.7 Open Loop Power Control of [9]
|
40bd05ebf1e9d686c3dc55dd3e817398
|
34.122
|
5.4.1.3.4.2 Procedure
|
1) Set the TX output level of the SS to obtain Îor at the UE antenna connector. Îor shall be according to table 5.4.1.3.4b (-25 dBm / 1,28 MHz).
2) Measure the UpPCH TX mean power of UE.
3) Repeat the above measurement for all SS levels in table 5.4.1.3.4b.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.