hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.3 Timeslot ISCP | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.3.1 Explanation | The result of this measurement is not energy and it is independent with the bandwidth, so there should not be modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.4 UTRA carrier RSSI | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.4.1 Explanation | This measurement relies on the signal-detecting algorithm which independent with the bandwidth and chip rate, so it needs no modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.5 GSM carrier RSSI | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.5.1 Explanation | This measurement relies on GSM, so it needs no modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.6 SIR | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.6.1 Explanation | This measurement mainly used to meet the requirement of service performance which independent with the bandwidth and chip rate, so there should be no modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.7 Transport channel BLER | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.7.1 Explanation | This measurement is mainly used to meet the requirement of service performance which independent with the bandwidth and chip rate, so there should be no modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.8 SFN-SFN observed time difference | The measurement period for CELL_DCH state can be found in section 4.5. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.8.1 Accuracy requirements | Table 4.9: SFN-SFN observed time difference accuracy
Parameter
Unit
Accuracy
Conditions
Io [dBm]
SFN-SFN observed time difference
Chip
+/-0,5 for type 1 but +/- 0.125 for type 2
-94...-50 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.8.2 Range/mapping | The reporting range for SFN-SFN observed time difference type 1 is from 0 ... 3276800 chip.
In table 4.10 mapping of the measured quantity is defined. Signalling range may be larger than the guaranteed accuracy range.
Table 4.10
Reported value
Measured quantity value
Unit
T1_SFN-SFN_TIME _0000000
0 SFN-SFN observed time difference type 1 < 1
chip
T1_SFN-SFN_TIME _0000001
1 SFN-SFN observed time difference type 1 < 2
chip
T1_SFN-SFN_TIME _0000002
2 SFN-SFN observed time difference type 1 < 3
chip
…
…
…
T1_SFN-SFN_TIME _3276797
3276797 SFN-SFN observed time difference type 1 < 3276798
chip
T1_SFN-SFN_TIME _3276798
3276798 SFN-SFN observed time difference type 1 < 3276799
chip
T1_SFN-SFN_TIME _3276799
3276799 SFN-SFN observed time difference type 1 < 3276800
chip
The reporting range for SFN-SFN observed time difference type 2 is from –6400 ... +6400 chip.
In table 4.11 mapping of the measured quantity is defined. Signalling range may be larger than the guaranteed accuracy range.
Table 4.11
Reported value
Measured quantity value
Unit
T2_SFN-SFN_TIME _00000
SFN-SFN observed time difference type 2 < -6390,00
chip
T2_SFN-SFN_TIME _00001
-6390,00 SFN-SFN observed time difference type 2 < -6399,75
chip
T2_SFN-SFN_TIME _00002
-6399,75 SFN-SFN observed time difference type 2 < -6399,50
chip
…
…
…
T2_SFN-SFN_TIME _51199
6399,50 SFN-SFN observed time difference type 2 < 6399,75
chip
T2_SFN-SFN_TIME _51200
6399,75 SFN-SFN observed time difference type 2 < 6400,00
chip
T2_SFN-SFN_TIME _51201
6400,00 SFN-SFN observed time difference type 2
chip |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.8.3 Explanation difference | In 1.28 Mcps TDD there are 12800chips per frame while in 3.84 Mcps TDD there are 38400chips. According to this chip number difference, the observed time difference range in type 1 should be changed correspondingly.
There are 3 kind of special time slot (DwPTS, UpPTS and GP) in 1.28 Mcps TDD frame structure (see section 7.2.1 ‘frame structure’ in TR 25.928). When calculation the SFN-SFN observed time difference in type 2, it needs to consider the position and affection of these 3 special time slots.
Let us suppose:
TRxTSi : time of start of timeslot#0 received of the serving TDD cell i.
TRxTSk : time of start of timeslot#0 received from the target UTRA cell k that is closest in time to the start of the timeslot of the serving TDD cell i.
SFN-SFN observed time difference = TRxTSk - TRxTSi, in chips, which means to calculate the the time difference of the start position of the current frame in cell i to the closest starting position of one frame in cell k.
Editor Note: Here in type 2 we only consider to measure the difference of two cells of 1.28 Mcps TDD. The measurement method is like that in TS 25.215. In type 2 measurement of TS 25.215, it measures the time difference of the start position of the P-CPICH of two cells. That is just something like in 1.28 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.9 Observed time difference to GSM cell | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.9.1 Explanation | For different systems, the measurement that is used to realize the compatibility should be the same. So it is independent with bandwidth and chip rate and there should be no modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.10 UE GPS Timing of Cell Frames for LCS | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.10.1 Explanation | The GPS timing of cell frames should be the same for different systems having LCS, so it needs no modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.11 SFN-CFN observed time difference | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.1.11.1 Explanation | For the measurement used for the interwork between cells, which belong to the same system or different systems, should be the same and independent with bandwidth and chip rate. So it needs no modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.2 Performance for UE Measurements in Uplink (TX) | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.2.1 UE transmitted power | Common with 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.1.2.1.1 Explanation | The UE transmitted power is represented by energy density and it is independent with the bandwidth, so there should not be modification. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2 Measurements Performance for UTRAN | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1 Performance for UTRAN Measurements in Uplink (RX) | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.1 RSCP | Common with 3.84 Mcps TDD option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.2 Timeslot ISCP | Common with 3.84 Mcps TDD option |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.3 RSSI | Common with 3.84 Mcps TDD option |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.4 SIR | Common with 3.84 Mcps TDD option |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.5 Transport Channel BER | Common with 3.84 Mcps TDD option |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.6 RX Timing Deviation | The definition of RX Timing Deviation here is common with 3.84 Mcps but only accuracy and range are different between two TDD mode. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.6.1 Accuracy requirements | Table 4.12
Parameter
Unit
Accuracy
Conditions
Range [chips]
RX Timing Deviation
chips period
+/- 0.125
-128, …, 128 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.6.2 Range/mapping | The reporting range for RX Timing Deviation is from-128 ... 128 chips.
In table 4.13 mapping of the measured quantity is defined. Signaling range may be larger than the guaranteed accuracy range.
Table 4.13
Reported value
Measured quantity value
Unit
RX_TIME_DEV_0001
RX Timing Deviation < –128,000
chip
RX_TIME_DEV_0002
-128,000 RX Timing Deviation < -127,875
chip
RX_TIME_DEV_0003
-127,875 RX Timing Deviation < -127,750
chip
…
…
…
RX_TIME_DEV_1024
000,000 RX Timing Deviation < 000,125
chip
…
…
…
RX_TIME_DEV_2046
127,750 RX Timing Deviation < 127,875
chip
RX_TIME_DEV_2047
127,875 RX Timing Deviation < 128,000
chip
RX_TIME_DEV_2048
128,000 RX Timing Deviation
chip
NOTE: This measurement can be used for timing advance (synchronisation shift) calculation for uplink synchronisation or location services. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.6.3 Explanation difference | In 3.84 Mcps TDD the ‘RX Timing Deviation’ measurement is only needed to report to the higher layer for timing advance calculation or location services. It does not need to measure this value continuously.
While in 1.28 Mcps TDD this measurement is not only reported to higher layer, but also severed as a physical signal (‘Synchronization Shift’ or ‘SS’) to keep uplink synchronization. It needs to be refreshed every 5ms (every sub-frame). The resolution requirement is 1/8 chip as described in section 10.2 ‘Timing Advance’ of TR25.928 [10].
Because SS is served as a physical layer signal in 1.28 Mcps TDD, it needs to consider how to map this value onto data burst. When in random access procedure the SS control step should have a large range to quickly establish the uplink synchronization. While in normal working procedure to maintain the uplink synchronization it should use as little bits as possible to reduce the affection to the DPCH capacity. These considerations are described in section 10.2 ‘Timing Advance’ and section 8.2.2 ‘Coding of Synchronization Shift’ of TR25.928 [10].
Others section of 4.6.2.1 are common with 25.123 [3] |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.7 SYNC-UL Timing Deviation for 1.28 Mcps | This measurement refers to TS 25.225 [13]subsection 5.2.8.1. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.7.1 Accuracy requirements | Table 4.14
Parameter
Unit
Accuracy
Conditions
Range [chips]
SYNC-UL Timing Deviation
chips period
+/- 0.125
0, …, 255.875 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.7.2 Range/mapping | The reporting range for SYNC-UL Timing Deviation is from 0 ... 255.875 chips.
In table 4.15 the mapping of the measured quantity is defined. Signaling range may be larger than the guaranteed accuracy range.
Table 4.15
Reported value
Measured quantity value
Unit
SYNC_UL_TIME_DEV_0000
SYNC-UL Timing Deviation < 0
chip
SYNC_UL_TIME_DEV_0001
0 SYNC-UL Timing Deviation < 0.125
chip
SYNC_UL_TIME_DEV_0002
0.125 SYNC-UL Timing Deviation < 0.25
chip
…
…
…
SYNC_UL_TIME_DEV_1024
127.875 SYNC-UL Timing Deviation < 128
chip
…
…
…
SYNC_UL_TIME_DEV_2045
255.625 SYNC-UL Timing Deviation < 255.75
chip
SYNC_UL_TIME_DEV_2046
255.75 SYNC-UL Timing Deviation < 255.875
chip
SYNC_UL_TIME_DEV_2047
255.875 SYNC-UL Timing Deviation
chip
NOTE: This measurement can be used for timing advance (synchronisation shift) calculation for uplink synchronisation or location services. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.1.7.3 Explanation difference | In 1.28 Mcps TDD there is a two step approach for the random access procedure. In the first step the UpPCH is transmitted by the UE. The node B received the UpPCH and responds with the FPACH which contains the received position of the SYNC-UL sequence. This allows the UE to adjust its timing advance for the PRACH in order to allow the node B to receive the PRACH synchronously with the other physicals channels in the time slot carrying the PRACH.
As there is a special time slot of random access in 3.84 Mcps TDD there is no need for this measurement in 3.84 Mcps TDD. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.2 Performance for UTRAN Measurements in Downlink (TX) | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.2.1 Transmitted carrier power | Common with 3.84 Mcps TDD option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.2.1.1 Explanation | These parameters in this section are not energy ,so they are independent with bandwidth . There need not to any change compare with the 3.84 Mcps TDD option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.6.2.2.2 Transmitted code power | Common with 3.84 Mcps TDD option.
4.6.2.2.2.1 explanation
These parameters in this section are not energy ,so they are independent with bandwidth. There need not to any change compare with the 3.84 Mcps TDD option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.7 FPACH physical layer information field definition (1.28 Mcps TDD) | 1.28 Mcps TDD introduces the FPACH (Forward Physical Access CHannel) which carries physical layer information. Two of these information fields are the ‘received starting position of the UpPCH’ (Uplink Pilot CHannel) and the ‘transmit power level command for the RACH message’. Both information fields are directly (received starting position of the UpPCH) or can be indirectly (transmit power level command for the RACH message) derived from measurements but are no measurements themselves. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.7.0 Explanation difference | In 1.28 Mcps TDD the random access procedure follows a two step approach. After the 1st step (UpPCH) the FPACH also carries the information fields related to the initialisation of uplink synchronisation control and uplink power control for the PRACH (2nd step). This is ensuring that the PRACH can be transmitted in the time slots carrying the DPCH. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.7.1 Received starting position of the UpPCH (UpPCHPOS) (1.28 Mcps TDD) | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.7.1.1 Range/mapping | Table 4.16
Range/mapping
UpPCHPOS FIELD is given with a resolution of 1/8 chip with the range [0,255.875] chip.
UpPCHPOS FIELD shall be transmitted in the FPACH where:
UpPCHPOS FIELD_LEV_0000: UpPCHPOS < 0 chip
UpPCHPOS FIELD_LEV_0001: 0 chip UpPCHPOS < 0.125 chip
UpPCHPOS FIELD_LEV_0002: 0.125 chip UpPCHPOS < 0.25 chip
...
UpPCHPOS FIELD_LEV_2045: 255.625 chip UpPCHPOS < 255.75 chip
UpPCHPOS FIELD_LEV_2046: 255.75 chip UpPCHPOS < 255.875 chip
UpPCHPOS FIELD_LEV_2047: 255.875 chip UpPCHPOS |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.7.1.2 Accuracy requirements | Table 4.17
Parameter
Unit
Accuracy
Conditions
Range [chips]
Received starting position of the UpPCH
chips period
+/- 0.125
0, …, 255.875 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.7.2 Transmit Power Level Command for the RACH message (1.28 Mcps TDD) | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.7.2.1 Range/mapping | Table 4.18
Range/mapping
PRXPRACH,des FIELD is given with a resolution of 0.5 dB with the range [-120,-80] dBm.
PRXPRACH,des FIELD shall be transmitted in the FPACH where:
PRXPRACH,des FIELD_LEV_00: PRXPRACH,des < -120 dBm
PRXPRACH,des FIELD_LEV_01: -120 dBm PRXPRACH,des < -119.5 dBm
PRXPRACH,des FIELD_LEV_02: -119.5 dBm PRXPRACH,des < -119 dBm
...
PRXPRACH,des FIELD_LEV_78: -81 dBm PRXPRACH,des < -80.5 dBm
PRXPRACH,des FIELD_LEV_79: -80.5 dBm PRXPRACH,des < -80 dBm
PRXPRACH,des FIELD_LEV_80: -80 dBm PRXPRACH,des |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 4.7.2.2 Accuracy requirements | Since this is a desired RX power at the node B and this is no measured value and the derivation of this value in the node B is implementation specific, accuracy requirements are not applicable. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5 UE Radio Transmission and Reception | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.1 Frequency bands and channel arrangement | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.1.1 General | The information presented in this section is based on a chip rate of 1.28 Mcps. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.1.2 Frequency bands | Common with 3.84 Mcps TDD option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.1.3 TX–RX frequency separation | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.1.3.1 Description | No TX-RX frequency separation is required as Time Division Duplex (TDD) is employed. Each subframe of 1.28 Mcps TDD consists of 7 main timeslots (TS0 ~ TS6) where TS0 (before DL to UL switching point) are always allocated DL, the timeslots (at least the first one) before the switching point (vice versa) are allocated UL and the timeslots after the switching point (vice versa) are allocated DL. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.1.3.2 Explanation of difference | The frame structure for 3.84 Mcps TDD and 1.28 Mcps TDD is different. For 3.84 Mcps TDD, each TDMA frame consists of 15 timeslots where each timeslot can be allocated to either transmit or receive. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.1.4 Channel arrangement | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.1.4.1 Channel spacing | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.1.4.1.1 Background | The chip rate is 1.28 Mcps with a roll-off factor of 0.22, therefore the occupied bandwidth is1.6MHz. It is just nominal 1.6MHz, and it is also flexible to adjust the channel raster step 200kHz to narrow as 1.4MHz for strict requirement situations if needed. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.1.4.1.2 Channel spacing | The channel spacing for 1.28 Mcps chip rate option is 1.6MHz. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.1.4.2 Channel raster | Common with 3.84 Mcps TDD option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.1.4.3 Channel number | Common with 3.84 Mcps TDD option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2 Transmitter characteristics | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.1 General | Common with 3.84 Mcps TDD option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.2 Transmit power | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.2.1 User Equipment maximum output power | Common with 3.84 Mcps TDD option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.3 UE frequency stability | Common with 3.84 Mcps TDD option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.4 Output power dynamics | Power control is used to limit the interference level. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.4.1 Open loop power control | 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.1 |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.4.1.1 Minimum requirement | 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.
Table 5.1: Open loop power control
Normal conditions
± 9 dB
Extreme conditions
± 12 dB |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.4.2 Closed loop power control in the uplink | Closed loop power control in the Uplink is the ability of the UE transmitter to adjust its output power in accordance with one or more TPC commands received in the downlink. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.4.2.1 Power control steps | The power control step is the change in the UE transmitter output power in response to a single TPC command, TPC_cmd, arrived at the UE. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.4.2.1.1 Minimum requirement | The UE transmitter shall have the capability of changing the output power with a step size of 1, 2 and 3 dB according to the value of TPC or RP-TPC, in the slot immediately after the TPC_cmd can be arrived.
a) The transmitter output power step due to closed loop power control shall be within the range shown in Table 5.2
b) The transmitter average output power step due to closed loop power control shall be within the range shown in Table 5.3. Here a TPC_cmd group is a set of TPC_cmd values derived from a corresponding sequence of TPC commands of the same duration.
The closed loop power is defined as the relative power differences between averaged power of original (reference) timeslot and averaged power of the target timeslot without transient duration. 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.
Table 5.2: Transmitter power control range
TPC_ cmd
Transmitter power control range
1 dB step size
2 dB step size
3 dB step size
Lower
Upper
Lower
Upper
Lower
Upper
Up
+0.5 dB
+1.5 dB
+1 dB
+3 dB
+1.5 dB
+4.5 dB
Down
-0.5 dB
-1.5 dB
-1 dB
-3 dB
-1.5 dB
-4.5 dB
Table 5.3: Transmitter average power control range
TPC_ cmd group
Transmitter power control range after 10 equal TPC_ cmd groups
1 dB step size
2 dB step size
3 dB step size
Lower
Upper
Lower
Upper
Lower
Upper
Up
+8 dB
+12 dB
+16 dB
+24 dB
+24 dB
+36 dB
Down
-8 dB
-12 dB
-16 dB
-24 dB
-24 dB
-36 dB |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.4.3 Minimum transmit output power | The minimum controlled output power of the UE is when the power control setting is set to a minimum value. This is when both the closed loop and open loop power control indicate a minimum transmit output power is required. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.4.3.1 Minimum requirement | The minimum transmit power is defined as an averaged power in a time slot 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. The minimum transmit power shall be better than –49 dBm/1.28MHz. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.4.3.2 Rationale | For the power control issue, the open loop and closed loop power control procedure is introduced in 1.28 Mcps TDD option [4], basically has the similar requirements as that of UTRA FDD.
The minimum transmit output power is basically kept in line with 3.84 Mcps TDD mode, just considering the RRC measurement filter bandwidth is 1/3 of 3.84 Mcps TDD mode, so the figure is scaleable change accordingly. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.4.4 Out-of-synchronisation handling of output power | The UE shall monitor the DPCH quality in order to detect a loss of the signal on Layer 1. The thresholds Qout and Qin specify at what DPCH quality levels the UE shall shut its power off and when it may turn its transmitter on, respectively. The thresholds are not defined explicitly, but are defined by the conditions under which the UE shall shut its transmitter off and turn it on, as stated in this clause. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.4.4.1 Requirement | The parameters in Table 5.4 are defined using the DL reference measurement channel (12.2) kbps specified in Annex C.2.1, where the CRC bits are replaced by data bits, and with static propagation conditions.
Table 5.4: DCH parameters for test of Out-of-synch handling
Parameter
Unit
Value
dB
-1
dBm/1.28 MHz
-60
dB
See figure 1
Information Data Rate
kbps
12.2
TFCI
-
On
The conditions for when the UE shall shut its transmitter on and when it shall turn it on are defined by the parameters in Table 5.4 together with the DPCH power level as defined in Figure 5.1.
Figure 5.1: Conditions for out-of-synch handling in the UE.
The indicated thresholds Qout andQin are only informative.
The requirements for the UE are that
- The UE shall not shut its transmitter off before point B.
- The UE shall shut its transmitter off before point C, which is Toff = 200 ms after point B
- The UE shall not turn its transmitter on between points C and E.
- The UE shall turn its transmitter on before point F, which is Ton = 200 ms after Point E. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.4.4.2 Rationale | A test procedure was introduced for the case of testing the UE ability to shut down its power if the received power is bellow a certain limit. The power will be varied at the input of the 3.84 Mcps TDD Option UE according to the following figure:
Figure 5.2: Conditions for out-of-synch handling in the 3.84 Mcps TDD Option UE.
The indicated thresholds Qout andQin are only informative.
This entry point of the power is the sensitivity limit of the 3.84 Mcps TDD Option UE. According to the link level simulations in TR25.942 [6] the UE needs a IOR/IOC=0.4dB (-1.6dB+2dB margin) at DPCH_EC/IOR=-6dB for the required performance in case of 12.2kBit/sec service and AWGN propagation. That means also that the required DPCH_EC/IOC=-5.6dB. In the testcase of “out-of-sync handling” the test shall be carried out with IOR/IOC= -1dB. That means if the UE shall operate at the same BER limit described above the DPCH_EC/IOR shall be –4.6 dB. (DPCH_EC/IOR = (DPCH_EC/IOC)*( IOC/IOR )=-5.6db+1dB=-4.6dB).
Doing the same calculations for the 1.28 Mcps TDD Option UE, the required IOR/IOC=3.2dB (1.2dB+2dB margin) at DPCH_EC/IOR=-7dB. That means also that the required DPCH_EC/IOC=-3.8dB. Setting the IOR/IOC= -1dB for the test case the required DPCH_EC/IOR= (DPCH_EC/IOC)*( IOC/IOR )=-3.8db+1dB= -2.8dB. That is the entry point in the test case for the 1.28 Mcps TDD Option UE. A –2.6dB will be proposed for this entry point level to have a convenient scaling level from 3.84 Mcps TDD Option to 1.28 Mcps TDD Option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.5 Transmit ON/OFF power | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.5.1 Transmit OFF power | The transmit OFF power state is when the UE does not transmit. This parameter is defined as the maximum output transmit power within the channel bandwidth when the transmitter is OFF. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.5.1.1 Minimum Requirement | The requirement for transmit OFF power shall be better than 65dBm measured with a filter that has a Root-Raised Cosine (RRC) filter response with a roll off =0.22 and a bandwidth equal to the chip rate. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.5.1.2 Rational | In TDD mode, various users are transmitting and receiving on the same frequency band. A maximum transmit output power in the transmitter idle mode has to be defined not to affect other nearby receiving mobiles or BSs. Then received power due to a near by UE has to be required below the noise floor.
The maximum acceptable transmit off power level can be represented as follows
Transmit off power level [dBm] < -174 [dBm/Hz] + 10log(1.28M[Hz]) +NF+MCL,
Assuming a minimum coupling loss (MCL) of 40dB between mobiles and a noise figure (NF) of 9dB for the UE, then we can get:
Transmit off power level [dBm] < -113 +9+40=-64dBm,
I.e., the transmit off power level has to be below 64dBm.
A selected value of –65 dBm leads to minor degradation in the receiver sensitivity, and also leads to well compatible with 3.84 Mcps TDD option. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.5.2 Transmit ON/OFF Time mask | The time mask transmit ON/OFF defines the tramping time allowed for the UE between transmit OFF power and transmit ON power. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.5.2.1 Minimum Requirement | The transmit power level versus time shall meet the mask specified in figure 5.3, where the transmission period refers to the burst without guard period for a single transmission slot, and to the period from the beginning of the burst in the first transmission slot to the end of the burst without guard period in the last transmission timeslot for consecutive transmission slots.
Figure 5.3: Transmit ON/OFF template |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.5.2.1 Rationales | A time mask should be included for relevant UE transmit power on/off scenarios. Requirements should be specified to limit impact on system performance and allow reasonable implementation.
To limit impact on the system performance, the time allowed for ramping should be small compared to the time period of continuous transmission. From implementation point of view ramping time should be as long as possible. Shorter ramping time will introduce more ripples in output power.
Depending on the size of a TDD cell it is required for the received signals from different users at the Node B be advanced in timing.
As described, there are four key parameters that have to be taken into account when specifying transmit time mask, especially when considering ramping during a guard period. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.5.2.1.1 Timing advance | For large cells, the timing advance is necessary, otherwise channel estimation will not work properly. Currently, a cell radius of having 8.7km for rural/macro case is assumed for illustration. This corresponds to round trip delay of 58s. 29us for timing advance is expected.. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.5.2.2 Switching time | Based on state-of-art semiconductor technology, about 10us of switching time could be expected to easy to handle and implementation in UE side. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.5.2.3 Delay spread | Under typical urban fading conditions, delay spread is mostly not greater than 3.125s (4chips) |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.5.2.4 BS Synchronization accuracy | The timing error of BSs synchronized to each other shall be less than 3.125us (4chips)
The figure 5.4 illustrates a situation,
Figure 5.4: Cell with timing advance
Based on above analysis and consideration, the 13chips(10us) period in 1.28 Mcps TDD UE is feasible for ramp up.
Considering the easy implementation aspects, a 20chips(about 15us) transient time is considered for ramp up when transmitter on.
For the ramp down transition in 1.28 Mcps TDD, the BS Synchronization error should be considered, there are 12chips(12.5-3.125=9.375us) period is proposed for TX ramp down. It is reasonable to implementation based on the state-of-art semiconductor level. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.6 Output RF spectrum emissions | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.6.1 Occupied bandwidth | |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.6.1.1 Description | Occupied bandwidth is a measure of the bandwidth containing 99% of the total integrated power for transmitted spectrum and is centered on the assigned channel frequency. The occupied channel bandwidth is about 1.6 MHz based on a chip rate of 1.28 Mcps. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.6.1.2 Explanation of difference | In 3.84 Mcps TDD, the occupied channel bandwidth is less than 5MHz based on 3.84 Mcps.
But in 1.28 Mcps TDD, as the background analysis in WG4#12 Meeting Tdoc515, which has been accepted to into the TR25.945, the occupied channel bandwidth should be less than 1.6 MHz based on 1.28 Mcps. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.6.2 Out of band emission | Out of band emissions are unwanted emissions immediately outside the nominal channel resulting from the modulation process and non-linearity in the transmitter but excluding spurious emissions. This out of band emission limit is specified in terms of a spectrum emission mask and adjacent channel power ratio. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.6.2.1 Spectrum emission mask | The spectrum emission mask of the UE applies to frequencies, which are between 0.8 and 4.0MHz from a carrier frequency. The out of channel emission is specified relative to the UE output power in measured in a 1.28 MHz bandwidth. |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.6.2.1.1 Minimum Requirement | The power of any UE emission shall not exceed the levels specified in Table 5.5.
Table 5.5: Spectrum Emission Mask Requirement (1.28 Mcps chip rate option)
Frequency offset from carrier Δf
Minimum requirement
Measurement bandwidth
0.8 MHz
-35 dBc
30 kHz
0.8-1.8 MHz
-35 – 14*(f-0.8) dBc
30 kHz
1.8-2.4 MHz
-49 – 17*(f-1.8)dBc
30 kHz
2.4 – 4.0MHz
-44 dBc
1MHz
NOTES: The first and last measurement position with a 30 kHz filter is 0.815 MHz and 2.385 MHz
The first and last measurement position with a 1 MHz filter is 2.9MHz and 3.5MHz
The lower limit shall be -55dBm/1.28 MHz or which ever is the higher.
Fig 5.5 Proposed spectrum emission mask measured in 30kHz bandwidth |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.6.2.1.2 Rationale | Based on the discussion, the mask in Table 5.6 is proposed for power class 5 (21 dBm), given in dBc compared with 21dBm/1.28MHz. The rationale for each specification point is outlined in the table together with the proposed mask and the corresponding mask values, measured in 30 kHz (the smallest measurement bandwidth used):
Table 5.6: Proposed spectrum emission mask values and rationale.
Frequency offset
f
Minimum requirement (whichever is lower)
Measurement bandwidth
Comments for rationale
Corresponding value in 30 kHz
0,8 MHz
(-14 dBm)
-35 dBc
30 kHz
Based on FCC part 24:
-13 dBm/14,6 kHz ;
And 1,28 Mcps TDD emission specification 1)
-35 dBc
0,8 - 1,8 MHz
-35 - 14*(f-0.8) dBc
30 kHz
Dropping linearly from 0,8 to 1 MHz 2)
1,8 MHz
(-28 dBm)
-49 dBc
30 kHz
Based on FCC part 24:
-13 dBm/1 MHz
-49 dBc
1,8 - 2,4 MHz
-49 - 17*(f-1.8) dBc
30 kHz3)
Based on ACLR @1,6 MHz
-33 dBc/1,28 MHz for 21 dBm UE 4)
2,4 - 4,0 MHz
(-28 dBm)
-44 dBc
1 MHz
Based on ACLR @3,2 MHz
-43 dBc/1,28 MHz for 21 dBm UE
-59.2 dBc |
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 5.2.6.2.1.2.1 Frequency offset | In FCC, frequency offset reference is the allocated band edge. Since spectrum definition has to be independent of operator allocation, the reference has been changed to the center frequency of the measured carrier. Assuming that the nominal carrier spacing is 1.6MHz for low chip rate TDD option, so spectrum mask definition starts at 0.8MHz offset. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.