hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
8.5.3.3.1 Definition and applicability
|
Common with 3.84 Mcps TDD option.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
8.5.3.3.2 Conformance requirements
|
For the parameters specified in table 8.27, the BLER should not exceed the piece-wise linear BLER curve specified in table 8.28.
Table 8.27: Parameters multipath Case 3 channel for 1.28 Mcps TDD option
Parameters
Unit
Test 1
Test 2
Test 3
Test 4
Number of DPCHo
4
1
1
0
Spread factor of DPCHo
8
8
8
dB
-7
-7
-7
–
Ioc
dBm/1.28 MHz
-91
Information Data Rate
kbps
12,2
64
144
384
Table 8.28: Performance requirements multipath Case 3 channel.
Test Number
[dB]
BLER
1
5.6
10-2
2
3.2
10-1
4.6
10-2
5.9
10-3
3
3.7
10-1
4.8
10-2
5.9
10-3
4
4.2
10-1
5.1
10-2
5.9
10-3
The reference for this requirement is subclause 6.4.3.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
8.5.3.3.3 Test purpose
|
Common with 3.84 Mcps TDD option.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
8.5.3.3.4 Method of test
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
8.5.3.3.4.1 Initial conditions
|
1) Connect the BS tester (UE simulator) generating the wanted signal and a set of interference generators to both BS antenna connectors for diversity reception via a combining network. The set of interference generators comprises a number of CDMA generators, each representing an individual intracell interferer (subsequently called DPCH0 generators) that the DPCH0s are synchronous, and an additional band-limited white noise source, simulating interference from other cells. Each DPCH0 generator shall produce an interfering signal that is equivalent to a valid 1.28 Mcps TDD signal with spreading factor 8, using the same time slot(s) than the wanted signal and applying the same cell-specific scrambling code. The number of the DPCH0 generators used in each test is given in table 8.27.
2) The wanted signal produced by the BS tester and the interfering signals produced by the DPCH0 generators are individually passed through independent Multipath Fading Simulators (MFS) before entering the combining network. Each MFS shall be configured to simulate multipath fading Case 3.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
8.5.3.3.4.2 Procedure
|
1) Adjust the power of the band-limited white noise source in such a way that its power spectral density measured at the BS antenna connector takes on the value Ioc as specified in table 8.27.
2) For a given test defined by the information data rate and the BLER objective, set the power of each DPCH0 measured at the BS antenna connector during the active time slots to the value specified in table 8.29.
3) Set up a call between the BS tester generating the wanted signal and the BS. The characteristics of the call shall be configured according to the information data rate to be provided and the corresponding UL reference measurement channel defined in Annex C.3. Depending on the information data rate, the UL reference measurement channel makes use of one or two Dedicated Physical Channels (DPCH1 and DPCH2) with different spreading factors SF. The power(s) of DPCH1 and DPCH2 (if applicable) measured at the BS antenna connector during the active time slots shall be set to the value(s) given in table 8.29.
4) Measure the BLER of the wanted signal at the BS receiver.
Table 8.29: Parameters of DPCH0 and the wanted signal
Test Number
BLER objective
Number of DPCH0
Power of each DPCH0 measured at the BS antenna connector [dBm]
Parameters of the wanted signal
DPCH
SF
Power measured at the BS antenna connector [dBm]
1
10-2
4
-92.4
DPCH1
8
-92.4
2
10-1
1
-94.8
DPCH1
2
-88.8
10-2
1
-93.4
DPCH1
2
-87.4
10-3
1
-92.1
DPCH1
2
-86.1
3
10-1
1
-94.3
DPCH1
2
-88.3
10-2
1
-93.2
DPCH1
2
-87.2
10-3
1
-92.1
DPCH1
2
-86.1
4
10-1
0
–
DPCH1
8
-93.8
DPCH2
2
-87.8
10-2
0
–
DPCH1
8
-92.9
DPCH2
2
-86.9
10-3
0
–
DPCH1
8
-92.1
DPCH2
2
-86.1
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
8.5.3.3.5 Test requirements
|
The BLER measured according to subclause 8.5.3.3.4.2 shall not exceed the limits specified in table 8.28.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
8.5.3.3.6 Explanation difference
|
For the 1.28 Mcps chip rate TDD option, one frame(10ms) consists of two subframes(5ms), and one subframe consists of 7 timeslots, (the structure of subframe is shown in TR 25.928). Considering the chip rate, the burst structure of 1.28 Mcps TDD for normal traffic is different from that of 3.84 Mcps TDD option, (the burst structure for normal traffic is shown in TR 25.928). So the propagation conditions, service mapping and simulation assumption of the measurement channel 12.2kps, 64pks, 144kps and 384kps should be different from those of 3.84 Mcps TDD option. As a result, the relevant parameters should be different.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9 RF System scenarios
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.1 General
|
To develop the 3GPP standard, all the relevant scenarios need to be considered and the most critical cases need to be identified for the various aspects of operation so that final parameters can be derived to meet both service and implementation requirements.
Parameters possibly influenced by the scenarios are listed in 25.102, 25.105 and 25.945. These include, but are not limited to:
- Out of band emissions;
- Spurious emissions;
- Intermodulation rejection;
- Intermodulation between MS;
- Blocking.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.2 Methodology for coexistence studies 1.28 Mcps TDD/FDD
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.2.1 Overview of the simulation
|
The focus of the simulations in the first step is on coexistence of macro cells considering a vehicular environment (case 3: 120km/h) with speech users only.
The simulation is a Monte-Carlo based snapshot method calculating CDFs for C/I for large numbers of stochastic mobile distributions over cells (including power control).
It should be pointed out that no kind of synchronisation or coordination between the different systems is assumed in the coexistence simulations presented here and before.
The goal of simulation procedure is to determine the relative capacity loss of a victim system for a considered link (uplink or downlink) due to the presence of a second system – the interfering system. The reference for the capacity loss is the capacity of the victim system alone without the interfering system.
The capacity of the system is defined as the mean number of mobile stations per cell (i.e. the load in different cells may be different while the mean load, i.e. the total number of users in the simulated scenario, remains constant) that can be active at a time while the probability that the C/I of a mobile station falls below a given threshold C/Imin is below 5% (i.e the percentage of users which do not satisfy the C/I criteria for the speech service is 5%).
This definition is different but strongly related to the so-called “satisfied user criterion” (i.e. 98% of all users have to be able to complete their call without being dropped due to interference). However the “satisfied user criterion” requires the mapping of C/I to BER/BLER values and time-continuous simulation techniques, while here a Monte Carlo snap shot method is used.
The simulation is done in two steps:
At first Nsingle the capacity of the single operator case (i.e. only the victim system is present) is determined which means that the capacity depends on the co-channel interference (i.e. there is no adjacent channel interference).
The co-channel interference power itself depends on a number of parameters, especially on the number of mobiles, their position and their power control behaviour. Nsingle is the maximum mean number of mobiles per cell that can be active at a time in the single operator case.
The second step is the calculation of the multi operator capacity (i.e. victim and interferer system are present) which means the maximum mean number of mobiles per cell Nmulti in the victim system that can be active at a time considering co-channel and adjacent channel interference.
To determine Nmulti the multi operator simulation is started with Nmulti =Nsingle. Due to the additional adjacent channel interference the outage of users with C/I below the threshold C/Imin is increased compared to the single operator case (5%).
By decreasing Nmulti until the outage of 5% is reached again the capacity loss due to adjacent channel interference can be determined.
(The number of users in the interfering system is chosen in that way that a single operator simulation with this system would result in an outage of 5%.)
Finally the relative capacity loss can be calculated as
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.2.2 Simulation parameters
|
Table 9.1: Receiver Parameters
No.
parameter
FDD
1.28 Mcps TDD
MS
BS
MS
BS
RX1
Sensitivity
dBm
-117
-121
-108
-110
RX2
Noise figure
dB
9
5
9
7
RX3
Antenna gain (incl. losses)
dBi
0
11
0
11
RX4
ACS
dB
33
45
33
45
RX5
Min. CIR for
8kbps speech
dB
-15.7
-20.9
-1.5
-6.7
Table 9.2: Transmitter Parameters
No.
Parameter
FDD
1.28 Mcps TDD
MS
BS
MS
BS
TX1
Max. TX power
dBm
21
43 (27 per user)
30
43 (33 per user)
TX2
Min.Tx power per user
dBm
-50
27-25=2
-44
33-30=3
TX3
Antenna gain
dB
See RX3
TX4
PC dynamic range (1 code considered)
dB
Max –(-50)
= 71
25
Max –(-44)
= 74
30
TX5
ACLR
dB
33 (43)
45 (50)
33 (43)
40 (50)
This section compares the different RF parameters for FDD and 1.28 Mcps TDD which are used to describe the "victim system" and the "interferer system" in the coexistence simulation scenarios.
As a first step concerning the minimum C/I ratio values of the 1.28 Mcps TDD system the following results were used:
- UL (i.e. receiving BS): C/Imin = -4.9dB
- DL (i.e. receiving MS): C/Imin = 0.3dB.
Considering the mapping of the information data bits for the 12.2kbps service in UL and DL: 244 bits are mapped on 536 bits. We assumed in a first approach that for a 8kbps speech service 244*(8kbps/12.2kbps) bits are mapped on 536bits which results in a subtraction of 1.83dB for the both C/Imin values mentioned before which finally leads to the values in the table.
The ACLR and ACS values were taken from the specifications TS 25.101, TS 25.102, TS 25.104, TS 25.105 and this report.
For the investigations the cluster size of the 1.28 Mcps TDD, i.e. the reuse of a frequency channel, may be chosen to be 1 (like for 3.84 Mcps TDD) or 3 (since the 1.28 Mcps TDD has one third of the bandwidth of the 3.84 Mcps TDD).
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.2.3 Scenarios
|
Figure 9.1
The scenarios considered in this document refer to the frequency range about 1920 MHz where TDD and FDD are allocated in adjacent frequency bands.
Since the TDD band may be used for uplink (UL) or downlink (DL) communication 3 different scenarios are of interest depending on which station (MS or BS) is receiving (RX) or transmitting (TX):
- TDD MS (UL TX) causes interference to FDD BS (RX of UL)
- FDD MS (UL TX) causes interference to TDD BS (RX of UL)
- FDD MS (UL TX) causes interference to TDD MS (RX of DL)
The reason for the adjacent channel interference is the non-ideal rise of transmit and receive filter flanks so that a leakage of transmitted power is the adjacent frequency band and a reception from adjacent frequency bands can not entirely be prevented.
To limit this interaction between different frequency bands ACLR (adjacent channel leakage power ratio) requirements for the transmitter and ACS (adjacent channel selectivity) requirements for the receiver are specified (see section before).
In the simulation for the 1.28 Mcps TDD mode spectrum emission masks are used fulfilling the ACLR requirements given in the section before.
Due to the adjacent channel interference superimposing with the co-channel interference contributions received both in the used frequency band it might happen that at the considered receiver station the C/I ratio is below a minimum C/I ratio (see section before) which is necessary for the considered service.
The percentage of these users is called ‘outage’.
The used Monte-Carlo based snapshot simulator determines at first for a given outage or noise raise the mean maximum number of mobiles per cell which can be active without adjacent channel interference (single operator case).
Usually an outage of 5% or a noise raise of 6dB (especially for FDD BS as victim, i.e. UL in FDD) is considered for a realistic maximum load of the cell.
Afterwards the mean number of users for the same outage/noise raise (as in the single operator case) is calculated taking into account the co-channel and the additional adjacent interference of the interferer system (multi operator case).
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.3 Methodology for coexistence studies 1.28 Mcps TDD / 3.84 Mcps TDD
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.3.1 Overview of Simulation
|
Same as subsection 9.2.1
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.3.2 Simulation parameters
|
This section compares the different simulation parameters for 3.84 Mcps TDD and 1.28 Mcps TDD which are used to describe the ‚victim system‘ and the ‚interferer system‘ in the coexistence simulation scenarios.
Table 9.3: General Parameters
No.
Parameter
a. 3.84 Mcps TDD
b. 1.28 Mcps TDD
MS
BS
MS
BS
P1
Chip rate
Mcps
3.84
1.28
P2
Frame length
ms; chip
10ms; 38400
10ms; 12800
P3
Slot length
ms;chip
666.666µs; 2560
675µs; 864
P4
Slots per frame
1
15
14
(+ pilots and guard period)
P5
Chip length
Ms
260.41666ns
781.25ns
P6
Sfmax
1
16
16
P7
Sfmin
1
1
1
P8
Size of data symbol alphabet
1
4 (QPSK)
4 (QPSK)
P9
No. of codes per TS
1
12
16
P10
No. of codes used for an 8kbps speech service
1
UL: 1x SF=16
DL: 1x SF=16
UL: 1x SF=16
DL: 1x SF=16
P11
User bandwidth
MHz
3.84
1.28
P12
Channel spacing
MHz
5
1.6
P13
Antenna position over ground
M
MS: 1.5m
BS: antenna height (15m) + average roof top level (12m) =27m
P14
Considered coverage area
Cell radius in m
Macro: 500m
P15
Considered cluster size
1
-
1
-
1
P16
Minimum coupling loss (MCL)
DB
BS-MS: 70, MS-MS: 35
BS-MS: 70, MS-MS: 35
Table 9.4: Receiver Parameters
No.
Parameter
a. 3.84 Mcps TDD
b. 1.28 Mcps TDD
MS
BS
MS
BS
RX1
Sensitivity
DBm
-105
-109
-108
-110
RX2
Noise figure
DB
9
5
9
7
RX3
Antenna gain (incl. losses)
DBi
0
11
0
11
RX4
ACS
DB
33
45
33
45
RX5
Min. CIR for
8kbps speech
DB
-5.6
-8.1
-1.5
-6.7
Table 9.5: Transmitter Parameters
No.
Parameter
a. 3.84 Mcps TDD
b. 1.28 Mcps TDD
MS
BS
MS
BS
TX1
Max. TX power
DBm
30
43 (36 per user)
30
43 (33 per user)
TX2
Min.Tx power per user
DBm
-44
36-30=6
-44
33-30=3
TX3
Antenna gain
DB
See RX3
TX4
PC dynamic range (1 code considered)
DB
Max –(-44)
= 74
30
Max –(-44)
= 74
30
TX5
ACLR
DB
33 (43)
45 (50)
33 (43)
40 (50)
As a first step concerning the minimum C/I ratio values of the 1.28 Mcps TDD system for the 8kbps speech service these results for a 12.2kbps service for case 3 were taken:
- UL (i.e. receiving BS): C/Imin = -4.9dB
- DL (i.e. receiving MS): C/Imin = 0.3dB.
Considering the mapping of the information data bits for the 12.2kbps service in UL and DL: 244 bits are mapped on 536 bits.
For an 8kbps speech service we assumed in a first approach that:
244 x (8kbps / 12.2kbps) bits are mapped on 536bits
which results in a subtraction of 1.83dB for the both C/Imin values mentioned before which finally lead to the values in the table.
For the 3.84 Mcps TDD system the minimum C/I requirements were taken from [8].
The ACLR and ACS values were taken from the specifications 25.102, 25.105 for 3.84 Mcps TDD and the report 25.945 for 1.28 Mcps TDD.
The cluster size of the 1.28 Mcps TDD, i.e. the reuse of a frequency channel, may be chosen to be 1 (like for 3.84 Mcps TDD) or 3 (since the 1.28 Mcps TDD has one third of the bandwidth of the 3.84 Mcps TDD). In our investigations we take cluster=1 as a first approach.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.3.3 Scenarios
|
Figure 9.2
The scenarios considered in this section refer to the frequency 1915MHz where 1.28 Mcps TDD and 3.84 Mcps TDD may be allocated in adjacent frequency bands.
In a first step the 1.28 Mcps TDD system is assumed to be a victim for ajacent channel interference of a 3.84 Mcps TDD system.
Since the TDD band may be used for uplink (UL) or downlink (DL) communication 3 different scenarios are of interest depending on which station (MS or BS) is receiving (RX) or transmitting (TX):
- 3.84 Mcps TDD MS (UL TX) causes interference to 1.28 Mcps TDD BS (RX of UL)
- 3.84 Mcps TDD MS (UL TX) causes interference to 1.28 Mcps TDD MS (RX of DL)
- 3.84 Mcps TDD BS (DL TX) causes interference to 1.28 Mcps TDD MS (RX of DL)
In a second step the 3.84 Mcps TDD system is the victim system suffering from adjacent channel interference of the 1.28 Mcps TDD system. Here 3 further cases need to be investigated:
- 1.28 Mcps TDD MS (UL TX) causes interference to 3.84 Mcps TDD BS (RX of UL)
- 1.28 Mcps TDD MS (UL TX) causes interference to 3.84 Mcps TDD MS (RX of DL)
- 1.28 Mcps TDD BS (DL TX) causes interference to 3.84 Mcps TDD MS (RX of DL)
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.4 Methodology for coexistence studies 1.28 Mcps TDD / 1.28 Mcps TDD
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.4.1 Overview of Simulation
|
Same as subsection 9.2.1
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.4.2 Simulation parameters
|
Same as subsection 9.3.2
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.4.3 Scenarios
|
Figure 9.3
In this section a scenario of two 1.28 Mcps TDD operators in the same geographic area is investigated. For both systems apart from the frequency bands the same rf parameters and again no synchronisation or coordination is assumed.
Since the TDD band may be used for uplink (UL) or downlink (DL) communication 3 different scenarios are of interest depending on which station (MS or BS) is receiving (RX) or transmitting (TX):
- 1.28 Mcps TDD MS (UL TX) causes interference to 1.28 Mcps TDD BS (RX of UL)
- 1.28 Mcps TDD MS (UL TX) causes interference to 1.28 Mcps TDD MS (RX of DL)
- 1.28 Mcps TDD BS (DL TX) causes interference to 1.28 Mcps TDD MS (RX of DL)
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.5 Results, implementation issues and recommendations
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.5.1 1.28 Mcps TDD /FDD
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.5.1.1 Simulation results
|
The results for the relative capacity loss are summarized in the table below.
Table 9.6
victim (receiver)
interferer (transmitter)
rel. capacity loss
FDD BS
1.28 Mcps TDD MS (cluster=1)
<2%
1.28 Mcps TDD BS
(cluster=1)
FDD MS
<2%
1.28 Mcps TDD MS
(cluster=1)
FDD MS
<2%
1.28 Mcps TDD MS
(cluster=3)
FDD MS
<3%
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.5.1.2 Conclusion
|
The focus of these investigations is on speech users in macro cells for a vehicular propagation environment.
The results show reasonable capacity loss values, even without coordination or time alignment between the victim and the interferer system.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.5.2 1.28 Mcps TDD / 3.84 Mcps TDD
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.5.2.1 Simulation results
|
The results for the relative capacity loss are summarized in the tables below.
1) For the case that the 1.28 Mcps TDD system suffers from adjacent channel, and interference from a 3.84 Mcps TDD system:
Table 9.7
Victim (receiver)
interferer (transmitter)
Relative capacity loss
1.28 Mcps TDD BS (cluster=1)
3.84 Mcps TDD MS
< 1%
1.28 Mcps TDD MS
(cluster=1)
3.84 Mcps TDD MS
< 2%
1.28 Mcps TDD MS
(cluster=1)
3.84 Mcps TDD BS
< 2%
2) For the case that the 3.84 Mcps TDD system suffers from adjacent channel, and interference from a 1.28 Mcps TDD system:
Table 9.8
Victim (receiver)
interferer (transmitter)
Relative capacity loss
3.84 Mcps TDD BS
1.28 Mcps TDD MS
(cluster=1)
<2%
3.84 Mcps TDD MS
1.28 Mcps TDD MS
(cluster=1)
< 1%
3.84 Mcps TDD MS
1.28 Mcps TDD BS
(cluster=1)
< 2%
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.5.2.2 Conclusion
|
The focus of these investigations is on speech users in macro cells for a vehicular propagation environment.
The results show reasonable capacity loss values, even without coordination or time alignment between the victim and the interferer system.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.5.3 1.28 Mcps TDD / 1.28 Mcps TDD
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.5.3.1 Simulation results
|
The results for the relative capacity loss are summarized in the table below.
Table 9.9
Victim (receiver)
interferer (transmitter)
relative capacity loss
1.28 Mcps TDD BS of operator A
(cluster=1)
1.28 Mcps TDD MS of operator B
(cluster=1)
< 2%
1.28 Mcps TDD MS of operator A
(cluster=1)
1.28 Mcps TDD MS of operator B
(cluster=1)
< 2%
1.28 Mcps TDD MS of operator A
(cluster=1)
1.28 Mcps TDD BS of operator B
(cluster=1)
< 1%
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.5.3.2 Conclusion
|
The focus of these investigations is on speech users in macro cells for a vehicular propagation environment.
The results show reasonable capacity loss values, even without coordination or time alignment between the victim and the interferer system.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.6 Information and General purpose materials
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.6.1 CDMA Definitions and Equations
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.6.1.1 CDMA-related definitions
|
The following CDMA-related abbreviations and definitions are used in various 3GPP WG4 documents.
Table 9.10
1.28M chips per second.
Average energy per PN chip for DwPTS.
The ratio of the received energy per PN chip for DwPTS to the total received power spectral density at the UE antenna connector.
The ratio of the average transmit energy per PN chip for DwPTS to the total transmit power spectral density.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.6.1.1.1 Explanation difference
|
For 1.28 Mcps chip rate TDD option, the frame length is 10ms and the 10ms is divided into 2 sub-frames of 5 ms. Each subframe is composed of 7 normal traffic time slots and two special pilot slots, i.e., DwPTS for downlink and UpPTS for uplink.
For 1.28 Mcps chip rate TDD option, the other CDMA related definitions have the same meaning as for 3.84 Mcps TDD.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.6.1.2 CDMA equations
|
The equations listed below describe the relationship between various parameters under different conditions.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.6.1.2.1 BS Transmission Power
|
Transmit power of the Base Station is normalized to 1 and can be presented as
(Normal downlink timeslots)
=1 (Timeslot 0)
=1 (DwPTS)
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.6.1.2.1.1 Explanations
|
1.28 Mcps TDD option has special frame structure; its TS0 is only used for downlink so the position of P-CCPCH is fixed. DwPTS and UpPTS are unique slots so separate equations are need for them.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7 Link Level performances
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1 Simulation results for 1.28 Mcps TDD performace
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.1 Simulation assumptions
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.1.1 Simulation chain
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.1.1.1 Downlink
|
Because joint detection is considered for the low chip rate TDD option, the simulation has to differ from the wideband TDD simulation. An orthogonal channel noise simulator (OCNS) can not be used, instead all intracell interferer have to be modelled individually. The simulation chain is shown in the figure below.
Figure 9.4: Downlink simulation chain
Ioc represents the intercell interference and other noise contributions, and DPCHoi for i=1 to m are the individual intracell interferer. Each intracell interferer DPCHoi is modelled by one code with Q=16. DPCH1 to DPCHn are the DPCH for the service under investigation. All DPCHi for i=1 to n and DPCHoj for j=1 to m have the same chip energy DPCH_Ec. Note that in the downlink all codes have a spreading factor of 16 for all reference measurement channels.
The ratio of Îor to Ioc is varied until the BLER target is reached, and
.
For the performance requirement test, the ratio of Îor to Ioc is increased by the implementation margin.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.1.1.2 Uplink
|
In the uplink the same simulation chain as for wide-band TDD is used. The uplink simulation chain is shown in figure9.5.
Figure 9.5: Uplink simulation chain
DPCH1 and DPCH2 are the DPCH for the service under investigation. DPCHoi for i=1 to n is one code with the spreading factor 8. The ratio of Îor to Ioc is varied until the BLER target is reached.
For the reference measurement channel one or two codes with different spreading factors are used. The following equations apply for the chip energy:
and
,
where Q1 and Q2 refer to the spreading factors of DPCH1 and DPCH2 and
.
If only a single code is used for the service under investigation, DPCH2_Ec is null. In this case the following formula applies:
The implementation margin is encountered in the intercell interference ratio Îor/Ioc.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.1.2 Simulation Assumptions
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.1.2.1 General
|
Table 9.11
Parameter
Explanation/Assumption
Chip Rate
1.28 Mcps
Duration of TDMA sub-frame
5 ms
Number of time slots per sub-frame
7
Closed loop power control
OFF
AGC
OFF
Number of samples per chip
1 sample per chip
Propagation Conditions
See Tdoc R400TDD051
Numerical precision
Floating point simulations
BLER target
10E-1; 10E-2; 10E-3
BLER calculation
BLER will be calculated by comparing with transmitted and received bits.
DCCH model
Random symbols transmitted, not evaluated in the receiver
TPC and SS model
Random symbols transmitted, not evaluated in the receiver
TFCI model
Random symbols, not evaluated in the receiver but it is assumed that receiver gets error free reception of TFCI information
Turbo decoding
Max Log Map with 4 iterations
Measurement Channels
See Tdoc R400TDD052
Other L1 parameters
As Specified in latest L1 specifications
Cell parameter
0 (this determines the scrambling and basic midamble code)
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.1.2.2 Additional downlink parameters
|
Table 9.12
Parameter
Value
Îor/Ioc
Ratio to meet the required BLER target
# of DPCHoi
Bit rate
Static
Case 1
Case 2
Case 3
12.2 kbps
8
8
8
8
64 kbps
2
2
2
2
144 kbps
2
2
2
2
384 kbps
0
0
0
0
Number of timeslots per sub-frame per user
12.2 kbps: TS=1
64 kbps: TS=1
144 kbps: TS=2
384 kbps: TS=4
Transmit diversity, “TxAA”, “TSTD”
OFF
Receiver antenna diversity
OFF
Midamble
Common midamble (See TR25.928v1.1.0 chapter 7.2.5)
Channelisation codes C(k; Q)
(see TR25.928v1.1.0 chapter 9.2.2)
12.2 kbps
64 kbps
144 kbps
384 kbps
DPCHi
C(i; 16)
C(i; 16)
C(i; 16)
C(i; 16)
DPCHoj
C(j+2; 16)
C(j+8; 16)
C(j+8; 16)
-
Receiver
Joint Detector (ZF-BLE)
Channel Estimation
Ideal multipath delay estimation and joint channel estimator according to article from Steiner and Baier in Freq., vol. 47, 1993, pp.292-298, based on correlation to obtain the complex amplitudes for the path.
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.1.2.3 Additional uplink parameters
|
Table 9.13
Parameter
Value
Channel Estimation
Ideal multipath delay estimation and joint channel estimator according to article from Steiner and Baier in Freq., vol. 47, 1993, pp.292-298, based on correlation to obtain the complex amplitudes for the path.
Receiver antenna diversity
ON (2 antennas)
Îor/Ioc [dB]
Parameter to meet the required BLER
# of DPCHoi
Bit rate
Static
Case 1
Case 2
Case 3
12.2 kbps
4
4
4
4
64 kbps
1
1
1
1
144 kbps
1
1
1
1
384 kbps
0
0
0
0
Number of timeslots per frame per user
12.2 kbps: TS=1
64 kbps: TS=1
144 kbps: TS=2
384 kbps: TS=4
Channelisation codes C(k; Q)
(see TR25.928v1.1.0 chapter 9.2.2)
12.2 kbps
64 kbps
144 kbps
384 kbps
DPCH1
C(1; 8)
C(1; 2)
C(1; 2)
C(1; 2)
DPCH2
-
-
-
C(5; 8)
DPCHoi
C(i+1; 8)
C(i+4; 8)
C(i+4; 8)
-
Midamble
UE specific (See TR25.928v1.1.0 chapter 7.2.5)
Receiver
Multi-User Detection (ZF-BLE)
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.2 Simulation results
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.2.1 12.2kps service
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.2.1.1 Graphical Presentation of 12.2kbps service UL Simulation Results
|
Figure 9.6
Figure 9.7
Figure 9.8
Figure 9.9
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.2.1.2 Graphical Presentation of 12.2kbps service DL Simulation Results
|
Figure 9.10
Figure 9.11
Figure 9.12
Figure 9.13
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.2.2 64kps Service
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.2.2.1 Graphical Presentation of 64kbps service UL Simulation Results
|
Figure 9.14
Figure 9.15
Figure 9.16
Figure 9.17
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.2.2.2 Graphical Presentation of 64kbps service DL Simulation Results
|
Figure 9.18
Figure 9.19
Figure 9.20
Figure 9.21
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.2.3 144kps Service
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.2.3.1 Graphical Presentation of 144kbps service UL Simulation Results
|
Figure 9.22
Figure 9.23
Figure 9.24
Figure 9.25
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.2.3.2 Graphical Presentation of 144kbps service DL Simulation Results
|
Figure 9.26
Figure 9.27
Figure 9.28
Figure 9.29
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.2.4 384kps Service
| |
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.2.4.1 Graphical Presentation of 384kbps service UL Simulation Results
|
Figure 9.30
Figure 9.31
Figure 9.32
Figure 9.33
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.1.2.4.2 Graphical Presentation of 384kbps service DL Simulation Results
|
Figure 9.34
Figure 9.35
Figure 9.36
Figure 9.37
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
9.7.2 1.28 Mcps TDD and FDD link level simulation
|
(void)
Annex A (informative):
The key physical layer parameters for low chip rate TDD option
Table A.1
Support of :
Difference to high chiprate TDD option
Further details
Support of different radio frame structure
1.Different frame structure to high chiprate TDD option
2.Different basic midamble sequences, maximum channel impulse response is scalable (W=8, 9, 12, 16, 21, 32, 64), depending on number of users and environment, including the association between midambles and channelisation codes
3.Use of only one burst type for physical channels except special bursts in DwPTS/UpPTS
4.Support of different timeslot formats due to different number of bits and L1 control signals and midamble length
5.Support of use of 8PSK for special timeslots/all timeslots per cell
6.Beacon function is provided by DwPTS and P-CCPCH
Segmentation of the radio frame into 2 subframes
Each subframe consists of 7 traffic slots (864 chips length) and two special timeslots for synchronisation and initial access which are separated by an extra guard period
5. Including TFCI, SS, and TPC coding (8PSK)
Modified Power Control
1.Closed Loop PC in uplink and downlink
2.Open loop PC on the SYNC1 Code while initial access
3.P-CCPCH and DwPTS power can be used as a beacon
4.number of TPC symbols can take 2 values
1. TPC bits also in downlink
3. transmit power level reported on BCH
4. none, one symbol, 16/SF TPC symbols per radio frame, number of TPC symbols is always the same like number of SS symbols
Modified RACH procedure
1.Random Access carried out in 2 steps
1. Send SYNC1, Receive FPACH
2. Send power controlled, timing advanced PRACH in traffic timeslot (code associated to received FPACH. There is another association between the PRACH and the FACH. These associations are broadcast by the BCH.)
Due to the two-step approach a collision most likely happens on the UpPTS. The RACH RUs are virtually collision free.
There are no dedicated RACH time slots, the RACH resources share the time slot with dedicated resources, a two step procedure ensures that the actual RACH.
Cell search operation
1.One synchronisation channel only (DwPTS) and different frame duration
Step 1: Search for DwPTS
Step 2: Scrambling- and basic midamble code identification
Step 3: searches for the head of multi-frame indicated
Step 4: Read the BCH
Uplink synchronisation
1.Special Layer1-SS symbols
2.Number of used SS symbols can take 2 values
3.SS-symbols are transmitted once per subframe
1.SS symbols command an incremental change of timing
2.none, one symbol, 16/SF SS symbols per radio frame, number of SS symbols is always the same like number of TPC symbols
3.Frequency and step size are configured by UTRAN (“k” and “M” parameters)
Beamforming
Beamforming applies to the dedicated channels and may also be used for some common channels like FPACH
Physical channels
P-CCPCH and S-CCPCH require two channelisation codes; FPACH is a new physical channel which always uses one channelisation code at SF 16.
Mapping of transport channels to physical channels
PCH; PICH and FACH can be time multiplexed with the BCH on the P-CCPCH. PCH, PICH and FACH can be time multiplexed on the S-CCPCH. Therefore these transport channels are using two channelisation codes of SF 16.
The PICH carries a different number of PIs than in the high chip rate option, because of the different burst structure.
Measurements
Ranges and accuracy have to be adapted for the low chip rate option.
Service mapping
Due to the different payload size and subframe segmentation the service mapping for the low chip rate differs from that of the high chip rate option.
Annex B (informative):
Test Cases
B.a Purpose of Annex
Same contents as TS 25.123 section A.1.
B.b Requirement classification for statistical testing
Same contents as TS 25.123 section A.2.
B.b.1 Types of requirements in TS 25.123
Same contents as TS 25.123 section A.2.1.
B.1 Idle Mode
B.1.1 Cell selection
This section is included for consistency in the numbering.
B.1.2 Cell Re-Selection
For each of the re-selection scenarios in section 4.2 a test is proposed.
For NTDD/NTDD re-selection two scenarios are considered:
Scenario 1: Single carrier case
Scenario 2: Multi carrier case
B.1.2.1 Single carrier case NTDD/NTDD cell re-selection
B.1.2.1.1 Test Purpose and Environment
This test is to verify the requirement for the cell re-selection delay in the single carrier case reported in section 4.2.
This scenario implies the presence of 1 carrier and 6 cells as given in Table B.1 and B.2. Cell 1 and cell2 shall belong to different Location Areas.
Table B.1: General test parameters for Single carrier NTDD/NTDD cell re-selection
Parameter
Unit
Value
Comment
Initial condition
Active cell
Cell1
Neighbour cells
Cell2, Cell3,Cell4, Cell5, Cell6
Final condition
Active cell
Cell2
Access Service Class (ASC#0)
‑ Persistence value
0..1
1
Selected so that no additional delay is caused by the random access procedure. The value shall be used for all cells in the test.
DRX cycle length
s
1.28
The value shall be used for all cells in the test.
T1
s
15
T2
s
15
Table B.2: Cell re-selection single carrier multi-cell case
Parameter
Unit
Cell 1
Cell 2
Cell 3
Timeslot Number
0
DWPTS
0
DWPTS
0
DWPTS
T1
T2
T1
T2
T1
T2
T1
T2
T1
T2
T1
T2
UTRA RF Channel Number
Channel 1
Channel 1
Channel 1
PCCPCH_Ec/Ior
dB
-3
-3
-3
-3
-3
-3
DwPCH_Ec/Ior
dB
0
0
0
0
0
0
dB
[9]
[7]
[9]
[7]
[7]
[9]
[7]
[9]
[-1]
[-1]
[-1]
[-1]
PCCPCH RSCP
dBm
[-64]
[-66]
[-66]
[-64]
[-74]
[-74]
Qoffset
[ 0]
[0 ]
[0]
[ 0]
[ 0]
[ 0]
Qhyst
[0 ]
[ 0]
[0]
[0 ]
[ 0]
[ 0]
Treselection
s
[ 0]
[ 0]
[0]
[ 0]
[ 0]
[ 0]
Sintrasearch
dB
not sent
not sent
not sent
not sent
not sent
not sent
Cell 4
Cell 5
Cell 6
Timeslot
0
DWPTS
0
DWPTS
0
DWPTS
T1
T2
T1
T2
T1
T2
T1
T2
T1
T2
T1
T2
UTRA RF Channel Number
Channel 1
Channel 1
Channel 1
PCCPCH_Ec/Ior
dB
-3
-3
-3
-3
-3
-3
DwPCH_Ec/Ior
dB
0
0
0
0
0
0
dB
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
PCCPCH RSCP
dBm
[-74]
[-74]
[-74]
[-74]
[-74]
[-74]
Qoffset
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
Qhyst
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
Treselection
s
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
Sintrasearch
dB
[ not sent]
[ not sent]
[ not sent]
[ not sent]
[ not sent]
[ not sent]
dBm/1.28 MHz
-70
Propagation Condition
AWGN
B.1.2.1.2 Test Requirements
The cell re-selection delay is defined as the time from the beginning of time period T2, to the moment when the UE camps on Cell 2, and starts to send the RRC CONNECTION REQUEST message to perform a Location Registration on cell 2.
The cell re-selection delay shall be less than 8 s.
NOTE:
The cell re-selection delay can be expressed as: TevaluateNTDD + TSI, where:
TevaluateNTDD A DRX cycle length of 1280ms is assumed for this test case, this leads to a Tevaluate NTDD of 6.4s according to Table 4.1 in section 4.2.2.7.
TSI Maximum repetition rate of relevant system info blocks that needs to be received by the UE to camp on a cell. 1280 ms is assumed in this test case.
This gives a total of 7.68 s, allow 8s in the test case.
B.1.2.2 NTDD/NTDD cell re-selection multi carrier case
B.1.2.2.1 Test Purpose and Environment
This test is to verify the requirement for the cell re-selection delay in the multi carrier case reported in section 4.1.2
This scenario implies the presence of 2 carriers and 6 cells as given in Table B-3 and B-4. Cell 1 and cell 2 shall belong to different Location Areas.
Table B.3: General test parameters for Cell Re-selection in Multi carrier case
Parameter
Unit
Value
Comment
Initial condition
Active cell
Cell1
Neighbour cells
Cell2, Cell3,Cell4, Cell5, Cell6
Final condition
Active cell
Cell2
Access Service Class (ASC#0)
– Persistence value
1
Selected so that no additional delay is caused by the random access procedure. The value shall be used for all cells in the test.
DRX cycle length
s
1.28
The value shall be used for all cells in the test.
T1
s
15
T2
s
15
Table B.4: Cell re-selection multi carrier multi cell case
Parameter
Unit
Cell 1
Cell 2
Cell 3
Timeslot Number
0
DWPTS
0
DWPTS
0
DWPTS
T1
T2
T1
T2
T1
T2
T1
T2
T1
T2
T1
T2
UTRA RF Channel Number
Channel 1
Channel 2
Channel 1
PCCPCH_Ec/Ior
dB
-3
-3
-3
-3
-3
-3
DwPCH_Ec/Ior
dB
0
0
0
0
0
0
dB
[9]
[7]
[9]
[7]
[7]
[9]
[7]
[9]
[-1]
[-1]
[-1]
[-1]
PCCPCH RSCP
dBm
[-64]
[-66]
[-66]
[-64]
[-74]
[-74]
Qoffset
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
Qhyst
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
Treselection
s
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
Qintrasearch
dB
[not sent]
[not sent ]
[not sent]
[not sent]
[not sent ]
[not sent]
Cell 4
Cell 5
Cell 6
Timeslot
0
DWPTS
0
DWPTS
0
DWPTS
T1
T2
T1
T2
T1
T2
T1
T2
T1
T2
T1
T2
UTRA RF Channel Number
Channel
Channel 2
Channel
PCCPCH_Ec/Ior
dB
-3
-3
-3
-3
-3
-3
DwPCH_Ec/Ior
dB
0
0
0
0
0
0
dB
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
PCCPCH RSCP
dBm
[-74]
[-74]
[-74]
[-74]
[-74]
[-74]
Qoffset
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
Qhyst
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
Treselection
s
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
Qintrasearch
dB
[not sent]
[not sent]
[not sent]
[not sent]
[not sent]
[not sent]
dBm/3.84 MHz
-70
Propagation Condition
AWGN
B.1.2.2.2 Test Requirements
The cell re-selection delay is defined as the time from the beginning of time period T2, to the moment when the UE camps on Cell 2, and starts to send the RRC CONNECTION REQUEST message to perform a Location Registration on cell 2.
The cell re-selection delay shall be less than 8 s.
NOTE: The cell re-selection delay can be expressed as: TevaluateNTDD + TSI, where:
TevaluateNTDD A DRX cycle length of 1280ms is assumed for this test case, this leads to a Tevaluate NTDD of 6.4s according to Table 4.1 in section 4.1.5.
TSI Maximum repetition rate of relevant system info blocks that needs to be received by the UE to camp on a cell. 1280 ms is assumed in this test case.
This gives a total of 7.68 s, allow 8s in the test case.
B.1.2.3 High chip rate TDD cell re-selection
B.1.2.3.1 Test Purpose and Environment
This test is to verify the requirement for the NTDD/TDD cell re-selection delay reported in section 4.1.2.3.
This scenario implies the presence of 1 low chip rate (NTDD) and 1 high chip rate (TDD) cell as given in Table B-5 and B-6.
The ranking of the cells shall be made according to the cell reselection criteria specified in TS 25.304.
For this test environment the ranking/mapping function indicated in the broadcast of cell 1 shall be in such a way as to enable the UE to evaluate that the NTDD cell 1 is better ranked as the TDD cell 2 during T1 and the TDD cell 2 is better ranked than the NTDD cell 1 during T2.
Cell 1 and cell 2 shall belong to different Location Areas.
Table B.5: General test parameters for TDD low chip rate to TDD high chip rate cell re-selection
Parameter
Unit
Value
Comment
Initial condition
Active cell
Cell1
NTDD cell
Neighbour cell
Cell2
TDD cell
Final condition
Active cell
Cell2
Access Service Class (ASC#0)
‑ Persistence value
1
Selected so that no additional delay is caused by the random access procedure. The value shall be used for all cells in the test.
DRX cycle length
s
1.28
T1
s
15
Cell 1 better ranked than cell 2
T2
s
15
Cell2 better ranked than cell 1
Table B.6: Test parameters for TDD low chip rate to TDD high chip rate cell re-selection
Parameter
Unit
Cell 1
Cell 2
Timeslot Number
0
DwPts
0
8
T1
T2
T 1
T 2
T1
T2
T 1
T 2
UTRA RF Channel Number
Channel 1
Channel 2
PCCPCH_Ec/Ior
dB
-3
-3
-3
-3
DwPCH_Ec/Ior
dB
0
0
n.a.
n.a.
SCH_Ec/Ior
dB
n.a.
n.a.
-9
-9
-9
-9
SCH_toffset
n.a.
n.a.
0
0
0
0
PICH_Ec/Ior
-3
-3
OCNS
dB
n.a.
n.a.
-4,28
-4,28
-4,28
-4,28
dB
[10]
[7]
[7]
[10]
[7]
[10]
dBm/3.84 MHz
-70
PCCPCH_RSCP
dBm
[-63]
[-66]
[-66]
[-63]
Treselection
s
0
0
Propagation Condition
AWGN
AWGN
B.1.2.3.2 Test Requirements
The cell re-selection delay is defined as the time from the beginning of time period T2, to the moment when the UE camps on Cell 2, and starts to send the RRC CONNECTION REQUEST message to perform a Location Registration on cell 2.
The cell re-selection delay shall be less than 8 s.
Note: The re-selection delay equals TTDDevaluate + Trep repetition period of the broadcast information of the selected cell
B.1.2.4 FDD cell re-selection
B.1.2.4.1 Test Purpose and Environment
This test is to verify the requirement for the NTDD/FDD cell re-selection delay reported in section 4.1.2.4.
This scenario implies the presence of 1 low chip rate TDD and 1 FDD cell as given in Table B-5 and B-6.
The ranking of the cells shall be made according to the cell reselection criteria specified in TS 25.304.
For this test environment the ranking/mapping function indicated in the broadcast of cell 1 shall be in such a way as to enable the UE to evaluate that the NTDD cell 1 is better ranked as the FDD cell 2 during T1 and the FDD cell 2 is better ranked than the NTDD cell 1 during T2.
Cell 1 and cell 2 shall belong to different Location Areas.
Table B.7: General test parameters for the TDD/FDD cell re-selection
Parameter
Unit
Value
Comment
Initial condition
Active cell
Cell1
NTDD cell
Neighbour cells
Cell2
FDD cell
Final condition
Active cell
Cell2
Access Service Class (ASC#0)
‑ Persistence value
1
Selected so that no additional delay is caused by the random access procedure. The value shall be used for all cells in the test.
DRX cycle length
s
1.28
The value shall be used for all cells in the test.
T1
s
15
T2
s
15
Table B.8: Test parameters for the NTDD/FDD cell re-selection
Parameter
Unit
Cell 1
Cell 2
Timeslot Number
0
DwPts
n.a.
T1
T2
T 1
T 2
T1
T2
UTRA RF Channel Number
Channel 1
Channel 2
PCCPCH_Ec/Ior
dB
-3
-3
-12
-12
DwPCH_Ec/Ior
dB
0
0
n.a.
CPICH_Ec/Ior
dB
n.a.
n.a.
-10
-10
SCH_Ec/Ior
dB
n.a.
n.a.
-12
-12
PICH_Ec/Ior
-15
-15
OCNS
dB
n.a.
n.a.
-0,941
-0,941
dB
[ ]
[ ]
[ ]
[ ]
dBm/1.28 MHz
-70
PCCPCH_RSCP
dBm
[ ]
[ ]
n.a.
n.a.
CPICH_Ec/Io
n.a.
[ ]
[ ]
Treselection
s
0
0
Propagation Condition
AWGN
B.1.2.4.2 Test Requirements
The cell re-selection delay is defined as the time from the beginning of time period T2, to the moment when the UE camps on Cell 2, and starts to send preambles on the PRACH for sending the RRC CONNECTION REQUEST message to perform a Location Registration on cell 2.
The cell re-selection delay shall be less than 8 s.
NOTE:
The cell re-selection delay can be expressed as: TevaluateFDD + TSI, where:
TevaluateFDD See Table 4.1 in section 4.1.5.
TSI Maximum repetition rate of relevant system info blocks that needs to be received by the UE to camp on a cell. 1280 ms is assumed in this test case.
This gives a total of 7.68 s, allow 8s in the test case.
B.1.3 Inter-RAT( GSM) cell re-selection
B.1.3.1 Scenario
B.1.3.1.1 Test Purpose and Environment
This test is to verify the requirement for the UTRAN to GSM cell re-selection delay reported in section 4.1.3
This scenario implies the presence of 1 UTRAN serving cell, and 1 GSM cell to be re-selected. Test parameters are given in Table, B-9, B-10, B-11.
The ranking of the cells shall be made according to the cell reselection criteria specified in TS 25.304.
For this test environment the ranking/mapping function indicated in the broadcast of cell 1 shall be in such a way as to enable the UE to evaluate that the NTDD cell 1 is better ranked as the GSM cell 2 during T1 and the GSM cell 2 is better ranked than the NTDD cell 1 during T2.
Table B.9: General test parameters for UTRAN (NTDD) to GSM Cell Re-selection
Parameter
Unit
Value
Comment
Initial condition
Active cell
Cell1
Neighbour cell
Cell2
Final condition
Active cell
Cell2
DRX cycle length
s
1.28
T1
s
15
T2
s
15
Table B.10: Cell re-selection UTRAN to GSM cell case (cell 1)
Parameter
Unit
Cell 1 (UTRA)
Timeslot Number
0
DwPTS
T1
T2
T1
T2
UTRA RF Channel Number
Channel 1
Channel 1
PCCPCH_Ec/Ior
dB
-3
-3
DwPCH_Ec/Ior
dB
0
0
dB
[9]
[7]
[9]
[7]
dBm/1.28 MHz
–70
–70
PCCPCH RSCP
dBm
[-64]
[-66]
Propagation Condition
AWGN
AWGN
Cell_selection_and_
reselection_quality_measure
P-CCPCH RSCP
Treselection
s
[ ]
SsearchRAT
dB
[ ]
Table B.11: Cell re-selection UTRAN to GSM cell case (cell 2)
Parameter
Unit
Cell 2 (GSM)
T1
T2
Absolute RF Channel Number
ARFCN 1
RXLEV
dBm
-80
-70
RXLEV_ACCESS_
MIN
dBm
[-100
MS_TXPWR_MAX_
CCH
dBm
30
B.1.3.1.2 Test Requirements
The cell re-selection delay is defined as the time from the beginning of time period T2, to the moment when the UE camps on Cell 2, and starts to send LOCATION UPDATING REQUEST message to perform a Location update.
The cell re-selection delay shall be less than [8] s.
NOTE: The UE shall keep a running average of 4 measurements, thus gives 4*1280ms (TmeasureGSM Table 4.1), means 5.12 seconds can elapse from the beginning of time period T2 before the UE has finished the measurements to evaluate that the GSM cell fulfils the re-selection criteria.
The cell selection parameters in the BCCH of the GSM cell in system info 3 and 4 are transmitted at least every second.
B.2 UTRAN Connected Mode Mobility
B.2.1 1.28 Mcps TDD/TDD Handover
(void)
B.2.2 1.28 Mcps TDD/FDD Handover
NOTE: This section is included for consistency with numbering with section 4.2, currently no test covering requirements in sections 4.2.2.2.1 and 4.2.2.2.2 exists.
B.2.3 1.28 Mcps TDD/GSM Handover
NOTE: This section is included for consistency with numbering with section 4.2 currently no test covering requirements in sections 4.2.3.2.1 and 4.2.3.2.2 exists.
B.2.4 Cell Re-selection in CELL_FACH
B.2.4.1 One frequency present in neighbour list
B.2.4.1.1 Test Purpose and Environment
Note: Cell reselection in Cell-fach is still under discussion.
The purpose of this test is to verify the requirement for the cell re-selection delay in CELL_FACH state in the single carrier case reported in section 4.2.4.2.1.1.
The test parameters are given in Table B.12 and B.13
Table B.12: General test parameters for Cell Re-selection in CELL_FACH
Parameter
Unit
Value
Comment
initial condition
Active cell
Cell1
Neighbour cells
Cell2, Cell3,Cell4, Cell5, Cell6
final condition
Active cell
Cell2
T1
s
T1 need to be defined so that cell re-selection reaction time is taken into account.
T2
s
T2 need to be defined so that cell re-selection reaction time is taken into account.
Table B.13: Cell specific test parameters for Cell Re-selection in CELL_FACH
Parameter
Unit
Cell 1
Cell 2
Cell 3
Timeslot Number
0
DWPTS
0
DWPTS
0
DWPTS
T1
T2
T1
T2
T1
T2
T1
T2
T1
T2
T1
T2
UTRA RF Channel Number
Channel 1
Channel 1
Channel 1
PCCPCH_Ec/Ior
DB
-3
-3
-3
-3
-3
-3
DwPCH_Ec/Ior
DB
0
0
0
0
0
0
DB
[9]
[7]
[9]
[7]
[7]
[9]
[7]
[9]
[-1]
[-1]
[-1]
[-1]
PCCPCH RSCP
DBm
-64
-66
-66
-64
-74
-74
Qoffset
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
Qhyst
DBm
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
Treselection
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
Qintrasearch
DB
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
Cell 4
Cell 5
Cell 6
Timeslot
0
DWPTS
0
DWPTS
0
DWPTS
T1
T2
T1
T2
T1
T2
T1
T2
T1
T2
T1
T2
UTRA RF Channel Number
Channel 1
Channel 1
Channel 1
PCCPCH_Ec/Ior
DB
-3
-3
-3
-3
-3
-3
DwPCH_Ec/Ior
DB
0
0
0
0
0
0
DB
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
PCCPCH RSCP
DBm
-74
-74
-74
-74
-74
-74
Qoffset
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
Qhyst
DBm
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
Treselection
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
Qintrasearch
DB
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
dBm/1.28 MHz
-70
Propagation Condition
AWGN
B.2.4.1.2 Test Requirements
The UE shall select cell 2 within a cell re-selection delay specified in 4.2.4.2.1.1
B.2.4.2 Two frequencies present in the neighbour list
B.2.4.2.1 Test Purpose and Environment
The purpose of this test is to verify the requirement for the cell re-selection delay in CELL_FACH state in section 4.2.4.2.1.2.The test parameters are given in Table B.14 and B.15.
Table B.14: General test parameters for Cell Re-selection in CELL_FACH
Parameter
Unit
Value
Comment
initial condition
Active cell
Cell1
Neighbour cells
Cell2, Cell3,Cell4, Cell5, Cell6
final condition
Active cell
Cell2
T1
s
T1 need to be defined so that cell re-selection reaction time is taken into account.
T2
s
T2 need to be defined so that cell re-selection reaction time is taken into account.
Table B.15: Cell specific test parameters for Cell re-selection in CELL_FACH state
Parameter
Unit
Cell 1
Cell 2
Cell 3
Timeslot Number
0
DWPTS
0
DWPTS
0
DWPTS
T1
T2
T1
T2
T1
T2
T1
T2
T1
T2
T1
T2
UTRA RF Channel Number
Channel 1
Channel 2
Channel 1
PCCPCH_Ec/Ior
DB
-3
-3
-3
-3
-3
-3
DwPCH_Ec/Ior
DB
0
0
0
0
0
0
DB
[9]
[7]
[9]
[7]
[7]
[9]
[7]
[9]
[-1]
[-1]
[-1]
[-1]
PCCPCH RSCP
DBm
[-64]
[-66]
[-66]
[-64]
[-74]
[-74]
Qoffset
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
Qhyst
DBm
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
Treselection
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
Qintrasearch
DB
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
Cell 4
Cell 5
Cell 6
Timeslot
0
DWPTS
0
DWPTS
0
DWPTS
T1
T2
T1
T2
T1
T2
T1
T2
T1
T2
T1
T2
UTRA RF Channel Number
Channel
Channel 2
Channel
PCCPCH_Ec/Ior
DB
-3
-3
-3
-3
-3
-3
DwPCH_Ec/Ior
DB
0
0
0
0
0
0
DB
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
[-1]
PCCPCH RSCP
DBm
[-74]
[-74]
[-74]
[-74]
[-74]
[-74]
Qoffset
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
Qhyst
DBm
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
Treselection
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
Qintrasearch
DB
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
dBm/1.28 MHz
-70
Propagation Condition
AWGN
NOTE: PCCPCH_RSCP is the quality measure for cell selection and re-selection.
B.2.4.2.2 Test Requirements
The UE shall select cell 2 within a cell re-selection delay specified in 4.2.4.2.1.
B.2.5 Cell Re-selection in CELL_PCH
Same requirements and test cases valid as for cell re-selection in idle mode.
B.2.6 Cell Re-selection in URA_PCH
Same requirements and test cases valid as for cell re-selection in idle mode.
B.3 Dynamic Channel Allocation
(void)
B.4 Timing characteristics
(void)
B.5 UE Measurements Procedures
B.5.1 1.28 Mcps TDD measurements
B.5.1.1 Event triggered reporting in AWGN propagation conditions
B.5.1.1.1 Test Purpose and Environment
This test will derive that the terminal makes correct reporting of an event Cell 1 is the active cell, Cell 2 is a neighbour cell on the used frequency. The power level on Cell 1 is kept constant and the power level of Cell 2 is changed using "change of best cell event" as illustrated in Figure B.1. The test parameters are shown in Table B.16. Hysteresis, absolute Threshold and Time to Trigger values are given in the table below and they are signalled from test device. In the measurement control information it is indicated to the UE that event-triggered reporting with Event 1G shall be used. P-CCPCH RSCP of the best cell has to be reported together with Event 1G reporting. New measurement control information, which defines neighbour cells etc., is always sent before the event starts.
Figure B.1: Illustration of parameters for handover measurement reporting test case
Table B.16
Parameter
Unit
Cell 1
Cell 2
Timeslot Number
0
DwPTS
0
DwPTS
T1
T2
T1
T2
T1
T2
T1
T2
UTRA RF Channel Number
Channel 1
Channel 2
PCCPCH_Ec/Ior
dB
-3
-3
DwPCH_Ec/Ior
dB
0
0
dB
[3]
[3]
-Infinity
[6]
dBm/1.28 MHz
-70
PCCPCH_RSCP
dBm
[-70]
[-70]
-Infinity
[-67]
Absolute Threshold (SIR)
dB
[ ]
Hysteresis
dB
[ ]
Time to Trigger
msec
[ ]
Propagation Condition
AWGN
NOTE: The DPCH of all cells are located in a timeslot other than 0.
B.5.1.1.1.1 Explanation difference
In 1.28 Mcps TDD the PICH is mapped onto P-CCPCH as describe in TR25.928. So the PICH-Ec/Ior is no longer used. The function of the SCH is achieved by DwPTS in 1.28 Mcps TDD and it is allocated to a dedicated timeslot. And the P-CCPCH is always mapped onto time slot 0, so time slot 8 is not considered in 1.28 Mcps TDD.
The parameter Îor/Ioc is measured to report to UE for its handover or cell selection and reselection.
B.5.1.1.2 Test Requirements
The UE shall send one Event 1G triggered measurement report, with a measurement reporting delay less than [480] ms from the beginning of time period T2.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
B.5.2 FDD measurements
B.5.2.1 Correct reporting of neighbours in AWGN propagation condition
B.5.2.1.1 Test Purpose and Environment
The purpose of this test is to verify that the UE makes correct reporting of an event when doing inter frequency measurements. The test will partly verify the requirements in section 4.5.1.2.2.
This test will derive that the terminal makes correct reporting of an event Cell 1 is the active cell, Cell 2 is a neighbour cell on the used frequency. The power level on Cell 1 is kept constant and the power level of Cell 2 is changed using "change of best cell event" as illustrated in Figure B.5.1. The test parameters are shown in Table B.5.2. Hysteresis, absolute Threshold and Time to Trigger values are given in the table below and they are signalled from test device. In the measurement control information it is indicated to the UE that event-triggered reporting with Event 2C shall be used. P-CCPCH RSCP of the best cell has to be reported together with Event 2C reporting. New measurement control information, which defines neighbour cells etc., is always sent before the event starts.
The test parameters are shown in Table B.17.
Table B.17: Cell Specific Parameters for Correct Reporting of Neighbours in AWGN Propagation Condition
Parameter
Unit
Cell 1
Cell 2
Timeslot Number
0
DwPTS
0
DwPTS
T1
T2
T1
T2
T1
T2
T1
T2
UTRA RF Channel Number
Channel 1
Channel 2
PCCPCH_Ec/Ior
dB
-3
-3
DwPCH_Ec/Ior
dB
0
0
dB
[3]
[3]
-Infinity
[6]
dBm/1.28 MHz
-70
PCCPCH_RSCP
dBm
[-70]
[-70]
-Infinity
[-67]
Absolute Threshold (SIR)
dB
[ ]
Hysteresis
dB
[ ]
Time to Trigger
msec
[ ]
Propagation Condition
AWGN
NOTE: The DPCH of all cells are located in a timeslot other than 0.
B.5.2.1.1.1 Explanation difference
In 1.28 Mcps TDD the PICH is mapped onto P-CCPCH as describe in TR25.928. So the PICH-Ec/Ior is no longer used. The function of the SCH is achieved by DwPTS in 1.28 Mcps TDD and it is allocated to a dedicated timeslot. And the P-CCPCH is always mapped onto time slot 0, so time slot 8 is not considered in 1.28 Mcps TDD.
B.5.2.1.2 Test Requirements
The UE shall send one Event 2C triggered measurement report, with a measurement reporting delay less than [5] s from the beginning of time period T2.
The UE shall not send any measurement reports, as long as the reporting criteria are not fulfilled.
B.6 Measurement Performance Requirements
B.6.1 Measurement Performance for UE
If not otherwise stated, the test parameters in table B.6.1 should be applied for UE RX measurements requirements in this clause.
B.6.1.1 TDD intra frequency measurements
If not otherwise stated, the test parameters in table B.18 should be applied for UE RX measurements requirements in this section.
Table B.18: Intra frequency test parameters for UE RX Measurements
Parameter
Unit
Cell 1
Cell 2
Timeslot Number
0
DwPTS
0
DwPTS
T1
T2
T1
T2
T1
T2
T1
T2
UTRA RF Channel Number
Channel 1
Channel 2
PCCPCH_Ec/Ior
dB
-3
-3
DwPCH_Ec/Ior
dB
0
0
dB
[3]
[3]
-Infinity
[6]
dBm/1.28 MHz
-70
Range 1:Io
Range 2:Io
dBm
-94..-70
–94..-50
-94..-70
–94..-50
Propagation condition
AWGN
NOTE 1: P-CCPCH_RSCP1,2 -[102] dBm.
NOTE 2: | P-CCPCH_RSCP1 – PCCPCH_RSCP2 | 20 dB.
NOTE 3: | Io – P-CCPCH_RSCP| [20] dB.
NOTE 4: Ioc level shall be adjusted according the total signal power Io at receiver input and the geometry factor Îor/Ioc.
NOTE 5: The DPCH of all cells are located in a timeslot other than 0
B.6.1.1.1 Explanation difference
In 1.28 Mcps TDD the PICH is mapped onto P-CCPCH as describe in TR25.928. So the PICH-Ec/Ior is no longer used. The function of the SCH is achieved by DwPTS in 1.28 Mcps TDD and it is allocated to a dedicated timeslot. And the P-CCPCH is always mapped onto time slot 0, so time slot 8 is not considered in 1.28 Mcps TDD.
The parameter Îor/Ioc is measured to report to UE for its handover or cell selection and reselection.
B.6.1.2 TDD inter frequency measurements
If not otherwise stated, the test parameters in table B.19 should be applied for UE RX measurements requirements in this section.
Table B.19: Intra frequency test parameters for UE RX Measurements
Parameter
Unit
Cell 1
Cell 2
Timeslot Number
0
DwPTS
0
DwPTS
T1
T2
T1
T2
T1
T2
T1
T2
UTRA RF Channel Number
Channel 1
Channel 2
PCCPCH_Ec/Ior
dB
-3
-3
DwPCH_Ec/Ior
dB
0
0
dB
[3]
[3]
-Infinity
[6]
dBm/1.28 MHz
-70
Range 1:Io
Range 2:Io
dBm
-94..-70
–94..-50
-94..-70
–94..-50
Propagation condition
AWGN
NOTE 1: P-CCPCH_RSCP1,2 -[102] dBm.
NOTE 2: | P-CCPCH_RSCP1 – PCCPCH_RSCP2 | 20 dB.
NOTE 3: | Io –P-CCPCH_RSCP1,2| [20] dB.
NOTE 4: Ioc level shall be adjusted according the total signal power Io at receiver input and the geometry factor Îor/Ioc.
NOTE 5: The DPCH of all cells are located in a timeslot other than 0
B.6.1.2.1 Explanation difference
In 1.28 Mcps TDD the PICH is mapped onto P-CCPCH as describe in TR25.928. So the PICH-Ec/Ior is no longer used. The function of the SCH is achieved by DwPTS in 1.28 Mcps TDD and it is allocated to a dedicated timeslot. And the P-CCPCH is always mapped onto time slot 0, so time slot 8 is not considered in 1.28 Mcps TDD.
The parameter Îor/Ioc is measured to report to UE for its handover or cell selection and reselection.
B.6.1.3 UTRA carrier RSSI inter frequency measurements
The table B.20 and notes 1,2 define the limits of signal strengths, where the requirement is applicable.
Table B.20: UTRA carrier RSSI Inter frequency test parameters
Parameter
Unit
Cell 1
Cell 2
UTRA RF Channei number
-
Channel 1
Channel 2
Îor/Ioc
DB
-1
-1
Ioc
dBm/1.28 MHz
Note 2
Note 2
Range 1: Io
Range 2: Io
dBm/1.28 MHz
-94…-70
-94…-50
-94…-70
-94…-50
Propagation condition
-
AWGN
NOTE 1: For relative accuracy requirement | Channel 1_Io –Channel 2_Io | < 20 dB.
NOTE 2: Ioc level shall be adjusted according the total signal power Io at receiver input and the geometry factor Îor/Ioc.
B.6.2 Measurement Performance for UTRAN
If not otherwise stated, the test parameters in table B.21 should be applied for UTRAN RX measurements requirements in this section.
Table B.21: Intra frequency test parameters for UTRAN RX Measurements
Parameter
Unit
Cell 1
UTRA RF Channel number
Channel 1
Timeslot
[ ]
DPCH Ec/Ior
dB
[ ]
Îor/Ioc
dB
[ ]
Ioc
dBm/1.28 MHz
-89
Range: Io
dBm
-105..-74
Propagation condition
AWGN
Annex C (informative):
Measurement Channels
C.1 General
(void)
C.2 Reference Measurement Channels (Downlink)
C.2.0 UL reference measurement channel (12.2 kbps, for definition of UE Tx parameters)
Table C.0
Parameter
Value
Information data rate
12.2 kbps
RU's allocated
1TS (1*SF8) = 2RU/5ms
Midamble
144
Interleaving
20 ms
Power control (TPC)
4 Bit/user/10ms
TFCI
16 Bit/user/10ms
4 Bit reserved for future use (place of SS)
4 Bit/user/10ms
Inband signalling DCCH
2.4 kbps
Puncturing level at Code rate 1/3: DCH / DCCH
33% / 33%
Figure C.0
C.2.0.1 Rationale
There is only one burst type for normal time slot in the low chip rate option. It provides the possibility for transmission of TFCI and TPC both in up- and downlink. The SS information will be used only in down link but in order to have the same burst structure for both directions the place of the SS bits are also reserved for up link and may be used in a future enhancement. Taking the mentioned features into consideration the up link multicode reference measurement channel can be the same as the down link 12.2kBit/s reference measurement channel (aligned to 3.84 Mcps TDD Option) with the exception that the SS bits are not used.
The following example will be used from WG1 with 3.4kBit/sec signalling (signalling can be varied between 1.7kBit/sec and 3.4kBit/sec):
NOTE: This example can be applied to multiplexing AMR speech and DCCH.
Figure C.0A: Channel coding and multiplexing example for multiplexing of 12.2 kbps data and 3.4 kbps data
Table C.0A: Physical channel parameters for multiplexing of 12.2 kbps data and 3.4 kbps data
Codes and time slots
SF8 x 1 code x 1 time slot
TFCI
16 bits per user
TPC + SS
2 bit + 2bit
In WG4 the performance simulations have been done with a signalling of 2.4kBit/sec (as an average signalling rate). So the mapping above will be modified for the 2.4kbit/sec signalling rate also.
C.2.1 DL reference measurement channel (12.2 kbps)
Table C.1
Parameter
Value
Information data rate
12.2 kbps
RU's allocated
1TS (2*SF16) = 2RU/5ms
Midamble
144
Interleaving
20 ms
Power control (TPC)
4 Bit/user/10ms
TFCI
16 Bit/user/10ms
Synchronisation Shift (SS)
4 Bit/user/10ms
Inband signalling DCCH
2.4 kbps
Puncturing level at Code rate 1/3: DCH / DCCH
33% / 33%
Figure C.1
C.2.2 DL reference measurement channel (64 kbps)
Table C.2
Parameter
Value
Information data rate
64 kbps
RU's allocated
1TS (8*SF16) = 8RU/5ms
Midamble
144
Interleaving
20 ms
Power control (TPC)
4 Bit/user/10ms
TFCI
16 Bit/user/10ms
Synchronisation Shift (SS)
4 Bit/user/10ms
Inband signalling DCCH
2.4 kbps
Puncturing level at Code rate: 1/3 DCH / ½ DCCH
32% / 0
Figure C.2
C.2.3 DL reference measurement channel (144 kbps)
Table C.3
Parameter
Value
Information data rate
144 kbps
RU's allocated
2TS (8*SF16) = 16RU/5ms
Midamble
144
Interleaving
20 ms
Power control (TPC)
8 Bit/user/10ms
TFCI
32 Bit/user/10ms
Synchronisation Shift (SS)
8 Bit/user/10ms
Inband signalling DCCH
2.4 kbps
Puncturing level at Code rate: 1/3 DCH / ½ DCCH
38% / 7%
Figure C.3
C.2.4 DL reference measurement channel (384 kbps)
Table C.4
Parameter
Value
Information data rate
384 kbps
RU's allocated
4TS (10*SF16) = 40RU/5ms
Midamble
144
Interleaving
20 ms
Power control (TPC)
16 Bit/user/10ms
TFCI
64 Bit/user/10ms
Synchronisation Shift (SS)
16 Bit/user/10ms
Inband signalling DCCH
Max.2 kbps
Puncturing level at Code rate: 1/3 DCH / ½ DCCH
41% / 12%
Figure C.4
C.2.4.1 Explanation difference
For the 1.28 Mcps chip rate TDD option, one frame (10ms) consists of two sub-frames(5ms), and one Sub-frame consists of 7 timeslots. The structure of timeslot in 1.28 Mcps chip rate TDD (shown inTR25.928) is different from the structure of timeslot in 3.84 Mcps TDD. So the service mapping of variance data rate of 1.28 Mcps chip rate TDD option is different from that of 3.84 Mcps chip rate TDD option.
C.2.5 BCH reference measurement channel
[mapped to 2 code SF16]
Table C.5
Parameter
Value
Information data rate:
12.3 kbps
RU´s allocated
2 RU
Midamble
144 chips
Interleaving
20 ms
Power control
0 bit
TFCI
0 bit
Puncturing level
13%
Figure C.5
C.2.5.1 Rationale
A test procedure was introduced for testing the UE BCH decoding performance. In WG1 the following service mapping for BCH was proposed:
Table C.6 : Parameters for BCH
Transport block size
246 bits
CRC
16 bits
Coding
CC, coding rate = 1/3
TTI
20 ms
Codes and time slots
SF = 16 x 2 codes x 1 time slot
TFCI
0 bit
TPC
0 bit
Figure C.6: Channel coding for BCH
According to that service mapping the following BCH reference measurement channel will be proposed.
C.2.6 UL multi code reference measurement channel (12.2 kbps)
Table C.7
Parameter
Value
Information data rate
12.2 kbps
RU's allocated
1TS (2*SF16) = 2RU/5ms
Midamble
144
Interleaving
20 ms
Power control (TPC)
4 Bit/user/10ms
TFCI
16 Bit/user/10ms
4 Bit reserved for future use (place of SS)
4 Bit/user/10ms
Inband signalling DCCH
2.4 kbps
Puncturing level at Code rate 1/3: DCH / DCCH
33% / 33%
Figure C.7
C.2.6.1 Rationale
A test procedure was introduced for testing the UE PA linearity. For that purpose two codes will be transmitted from the UE and will be analyzed (peak code domain error).
There is only one burst type for normal time slot in the low chip rate option. It provides the possibility for transmission of TFCI and TPC both in up- and downlink. The SS information will be used only in down link but in order to have the same burst structure for both directions the place of the SS bits are also reserved for up link and may be used in a future enhancement. Taking the mentioned features into consideration the up link multicode reference measurement channel can be the same as the down link 12.2kBit/s reference measurement channel (requirement is aligned to 3.84 Mcps TDD option) with the exception that the SS bits are not used.
C.3 Reference measurement channels (Uplink)
C.3.1 UL reference measurement channel (12.2 kbps)
Table C.8
Parameter
Value
Information data rate
12.2 kbps
RU's allocated
1TS (1*SF8) = 2RU/5ms
Midamble
144
Interleaving
20 ms
Power control (TPC)
4 Bit/user/10ms
TFCI
16 Bit/user/10ms
Synchronisation Shift (SS)
4 Bit/user/10ms
Inband signalling DCCH
2.4 kbps
Puncturing level at Code rate 1/3: DCH / DCCH
33% / 33%
Figure C.8
C.3.2 UL reference measurement channel (64 kbps)
Table C.9
Parameter
Value
Information data rate
64 kbps
RU's allocated
1TS (1*SF2) = 8RU/5ms
Midamble
144
Interleaving
20 ms
Power control (TPC)
4 Bit/user/10ms
TFCI
16 Bit/user/10ms
Synchronisation Shift (SS)
4 Bit/user/10ms
Inband signalling DCCH
2.4 kbps
Puncturing level at Code rate: 1/3 DCH / ½ DCCH
32% / 0
Figure C.9
C.3.3 UL reference measurement channel (144 kbps)
Table C.10
Parameter
Value
Information data rate
144 kbps
RU's allocated
2TS (1*SF2) = 16RU/5ms
Midamble
144
Interleaving
20 ms
Power control (TPC)
8 Bit/user/10ms
TFCI
32 Bit/user/10ms
Synchronisation Shift (SS)
8 Bit/user/10ms
Inband signalling DCCH
2.4 kbps
Puncturing level at Code rate: 1/3 DCH / ½ DCCH
38% / 7%
Figure C.10
C.3.4 UL reference measurement channel (384 kbps)
Table C.11
Parameter
Value
Information data rate
384 kbps
RU's allocated
4TS (1*SF2 + 1*SF8) = 40RU/5ms
Midamble
144
Interleaving
20 ms
Power control (TPC)
16 Bit/user/10ms
TFCI
64 Bit/user/10ms
Synchronisation Shift (SS)
16 Bit/user/10ms
Inband signalling DCCH
Max.2 kbps
Puncturing level at Code rate: 1/3 DCH / ½ DCCH
41% / 12%
Figure C.11
C.3.5 RACH reference measurement channel
Table C.12
Parameter
Value
Information data rate:
SF16 (RU’s allocated:1):
0% puncturing rate at CR=1/2
~10% puncturing rate at CR=1/2
SF8 (RU’s allocated:2):
0% puncturing rate at CR=1/2
~10% puncturing rate at CR=1/2
SF4 (RU’s allocated:4):
0% puncturing rate at CR=1/2
~10% puncturing rate at CR=1/2
BRACH =1
CRC length = 16
Tail Bits = 8
20 bits per frame and TB
24 bits per frame and TB
64 bits per frame and TB
73 bits per frame and TB
152 bits per frame and TB
170 bits per frame and TB
TTI
5msec
Midamble
144 chips
Power control
0 bit
TFCI
0 bit
NRACH = number of bits per TB
BRACH = number of TBs
NRM =puncturing rate
C.3.5.1 RACH mapped to 1 code SF16
Figure C.12
C.3.5.2 RACH mapped to 1 code SF8
Figure C.13
C.3.5.3 RACH mapped to 1 code SF4
Figure C.14
C.3.5.3.1 Explanation difference
For the 1.28 Mcps chip rate TDD option, one frame (10ms) consists of two sub-frames(5ms), and one Sub-frame consists of 7 timeslots. The structure of timeslot in 1.28 Mcps chip rate TDD (shown inTR25.928) is different from the structure of timeslot in 3.84 Mcps TDD. So the service mapping of variance data rate of 1.28 Mcps chip rate TDD option is different from that of 3.84 Mcps chip rate TDD option.
Annex D (informative):
Propagation conditions
D.1 Static Propagation conditions
The propagation for the static performance measurement is an Additive White Gaussian Noise (AWGN) environment. No fading and multi-path exist for the propagation model.
D.2 Multi-path fading propagation conditions
Table D.1 shows propagation conditions that are used for the performance measurements in multi-path fading environment. All taps have classical Doppler spectrum.
Table D.1: Propagation Conditions for Multi-Path Fading Environments
Case 1, speed 3km/h
Case 2, speed 3km/h
Case 3, speed 120km/h
Relative Delay [ns]
Average Power [dB]
Relative Delay [ns]
Average Power [dB]
Relative Delay [ns]
Average Power [dB]
0
0
0
0
0
0
2928
-10
2928
0
781
-3
12000
0
1563
-6
2344
-9
D.2.1 Rationale
The channel estimation can only resolve paths which are separated by at least one chip in delay. Otherwise the paths fall into the same tap. Even though this happens in realistic environments, it is not useful to base the propagation models for the performance requirements on a scenario with a delay spread of less than 1 chip, because the baseband is not tested in this case. Therefore, it is proposed to keep the same delay for the path in units of chips for the 1.28 Mcps chip rate TDD-mode as for the 3.84 Mcps chip rate TDD-mode. The tap delays in units of time are changed accordingly to take into account the difference in the chip rate. Due to the request to have the same maximum delay spread for 1.28 Mcps chip rate TDD as for 3.84 Mcps chip rate TDD, the delay spread of tap 3rd for the case 2 propagation conditions is set to 12 ms.
Annex E (informative):
Environmental conditions
E.1 General
This normative annex specifies the environmental requirements of the UE. Within these limits the requirements of this specifications shall be fulfilled.
E.2 Environmental requirements for the UE
The requirements in this clause apply to all types of UE(s)
E.2.1 Temperature
The UE shall fulfil all the requirements in the full temperature range of:
Table E.1
+15C – +35 C
for normal conditions (with relative humidity of 25 % to 75 %);
-10C ‑ +55C
for extreme conditions (see IEC publications 68‑2‑1 and 68‑2‑2)
Outside this temperature range the UE, if powered on, shall not make ineffective use of the radio frequency spectrum. In no case shall the UE exceed the transmitted levels as defined in TR25.945 UE Section for extreme operation.
E.2.2 Voltage
The UE shall fulfil all the requirements in the full voltage range, i.e. the voltage range between the extreme voltages.
The manufacturer shall declare the lower and higher extreme voltages and the approximate shutdown voltage. For the equipment that can be operated from one or more of the power sources listed below, the lower extreme voltage shall not be higher, and the higher extreme voltage shall not be lower than that specified below.
Table E.2
Power source
Lower extreme voltage
Higher extreme voltage
Normal conditions voltage
AC mains
0,9 * nominal
1,1 * nominal
nominal
Regulated lead acid battery
0,9 * nominal
1,3 * nominal
1,1 * nominal
Non regulated batteries:
Leclanché/lithium
Mercury/nickel cadmium
0,85 * nominal
0,90 * nominal
Nominal
Nominal
Nominal
Nominal
Outside this voltage range the UE if powered on, shall not make ineffective use of the radio frequency spectrum. In no case shall the UE exceed the transmitted levels as defined inTR25.945 UE section for extreme operation. In particular, the UE shall inhibit all RF transmissions when the power supply voltage is below the manufacturer declared shutdown voltage.
E.2.3 Vibration
The UE shall fulfil all the requirements when vibrated at the following frequency/amplitudes:
Table E.3
Frequency
ASD (Acceleration Spectral Density) random vibration
5 Hz to 20 Hz
0,96 m2/s3
20 Hz to 500 Hz
0,96 m2/s3 at 20 Hz, thereafter ‑3 dB/Octave
Outside the specified frequency range the UE, if powered on, shall not make ineffective use of the radio frequency spectrum. In no case shall the UE exceed the transmitted levels as defined in TR25.945 UE section for extreme operation.
E.2.4 Rationale
The environmental conditions of UE specification is kept in line with 3.84 Mcps TDD, because these specification do not consider the bandwidth of the signal nor any other difference between 3.84 Mcps TDD and 1.28 Mcps TDD.
Annex F (informative):
Terminal capabilities (TDD)
This section provides the UE capabilities related to this report.
Notes: This section shall be aligned with TS 25.306 [15] regarding TDD RF parameters. These RF UE Radio Access capabilities represent options in the UE, that require signalling to the network.
Table F.1 provides the list of UE radio access capability parameters and possible values for this report.
Table F.1: RF UE Radio Access Capabilities
UE radio access capability parameter
Value range
UE power class
(TR25.945 section 5.2.2.1)
2, 3
NOTE: Only power classes 2 and 3 are part of R99
Radio frequency bands
(TR25.945 section 5.1.2)
a), b), c), a+b), a+c), a+b+c)
Chip rate capability
(25.945)
1.28 Mcps
This section shall be aligned with TS 25.306 now, which includes the related chapters discussing both 3.84 Mcps TDD Option and 1.28 Mcps TDD Option UE Radio Access Capabilities. Therefore it is proposed to change some word descriptions in TR25.945.
Annex G (informative):
Methods of measurement
G.1 Emission
G.1.1 Methods of measurement and limits for EMC emissions
Common with 3.84 Mcps Chip rate TDD option.
G.1.2 Test configurations
Common with 3.84 Mcps Chip rate TDD option.
G.1.3 Radiated spurious emission from Base station and ancillary equipment
G.1.3.1 Radiated spurious emission, Base stations
G.1.3.1.1 Definition
Common with 3.84 Mcps Chip rate TDD option.
G.1.3.1.2 Test method
a) Common with 3.84 Mcps TDD option.
b) The BS shall transmit with maximum power declared by the manufacturer with all transmitters active. Set the base station to transmit a signal as stated in Table 8.3.2-1 of TR25.945.
c) The received power shall be measured over the frequency range 30 MHz to 12.75 GHz, excluding 4MHz below the first carrier frequency to 4 MHz above the last carrier frequency used. The measurement bandwidth shall be 100 kHz between 30 MHz and 1 GHz and 1 MHz above 1 GHz as given in ITU-R SM.329 [16]. The video bandwidth shall be approximately three times the resolution bandwidth. If this video bandwidth is not available on the measuring receiver, it shall be the maximum available and at least 1 MHz. At each frequency at which a component is detected, the maximum effective radiated power of that component shall be determined, as described in step a).
G.1.3.1.2.1 Explanation difference
To identify responses on receivers or duplex transceivers occurring during the test at discrete frequencies which are narrow band responses, the test shall be repeated with the unwanted signal frequency increased, and then decreased by several bandwidths.
Due to the different bandwidth of the low chip rate TDD option from that of the high chip rate TDD option, the frequency increased and/or decreased is changed from 10MHz to 3.2MHz, from 12.5MHz to 4MHz.
G.1.3.1.3 Limits
Common with 3.84 Mcps Chip rate TDD option.
G.1.3.2 Radiated spurious emission, Ancillary equipment
Common with 3.84 Mcps Chip rate TDD option.
G.1.4 Conducted emission DC power input/output port
Common with 3.84 Mcps Chip rate TDD option.
G.1.5 Conducted emissions, AC mains power input/output port
Common with 3.84 Mcps Chip rate TDD option.
G.1.6 Harmonic Current emissions (AC mains input port)
Common with 3.84 Mcps Chip rate TDD option.
G.1.7 Voltage fluctuations and flicker (AC mains input port)
Common with 3.84 Mcps Chip rate TDD option.
G.2 Immunity
Common with 3.84 Mcps Chip rate TDD option.
Annex H (informative):
Global in-channel Tx test
H.1 General
Description is common with 3.84 Mcps TDD option.
H.2 Definition of the process
H.2.1 Basic principle
Description is common with 3.84 Mcps TDD option.
H.2.2 Output signal of the Tx under test
Description is common with 3.84 Mcps TDD option
H.2.3 Reference signal
Description is common with 3.84 Mcps TDD option
H.2.4 Classification of measurement results
Description is common with 3.84 Mcps
H.2.5 Process definition to achieve results of type “deviation”
Description is common with 3.84 Mcps TDD option.
H.2.6 Process definition to achieve results of type “residual”
Description is common with 3.84 Mcps TDD option.
H.2.7 Error Vector Magnitude (EVM)
Description is common with 3.84 Mcps TDD option.
H.2.8 Peak Code Domain Error (PCDE)
Description is common with 3.84 Mcps TDD option.
H.3 Applications
This process may be applied in the measurements defined in the following subclauses:
8.3.3 Frequency Stability
8.3.4 Output Power Dynamics
|
1cc4b09fd057c9a5cf925fb9b5a5f4e7
|
25.945
|
8.3.8.2 Peak Code Domain Error
|
H.4 Notes
NOTE: Symbol length
Description is common with 3.84 Mcps TDD option
NOTE: Deviation
Description is common with 3.84 Mcps TDD option.
NOTE: Residual
Description is common with 3.84 Mcps TDD option.
NOTE: Scrambling code
Description is common with 3.84Mpcs TDD option.
NOTE: TDD
Description is common with 3.84 Mcps TDD option.
H.5 Rationale
The global in-channel Tx test enables the measurement of all relevant parameters that describe the in-channel quality of the output signal of the Tx under test in a single measurement process, not only FDD and all options of TDD.
Annex I (informative):
Change History
Table I.1: Change History
TSG / Date
Doc
CR
R
Title
Cat
Curr
New
Work Item
RP-15
Rel-5 version created by TSG RAN decision, no CRs
5.0.0
RP-23
RP-040038
0002
Correction of references to ITU recommendations
F
5.0.0
5.1.0
TEI5
RP-35
RP-070081
0004
CR on Changing SEM for LCR TDD
F
5.1.0
5.2.0
TEI5
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
1 Scope
|
The purpose of the present document is to help the relevant 3GPP groups to specify the changes to existing specifications, needed for the introduction of the “Handover for real-time services from PS domain” Building Block for Release 2000.
The purpose of this R00 work task is to define the relocation procedure to be used when real time services are supported in the PS domain.
The intention with this work item is to provide support for services such as voice over IP and multimedia over IP.
This TR focuses on the requirements for the solution. Possible solutions have been further studied and they are also described in this TR for comparison and evaluation against the requirements. In doing this work, RAN3 has identified some areas of study that are not primarily under RAN3’s responsibility. These are mentioned here so that work can be coordinated with the other 3GPP groups.
Changes to the signalling protocols in UTRAN and CN interfaces have also been studied at a high level.
This document is a ‘living’ document, i.e. it is permanently updated and presented to all TSG-RAN meetings.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
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] UMTS 23.009: "3rd Generation Partnership Project (3GPP) Technical Specification Group Core Network; Handover Procedures".
[2] UMTS 23.060: "3rd Generation Partnership Project (3GPP) Technical Specification Services and System Aspects; GPRS; Service Description".
[3] Handovers for real-time services from PS domain, Work Item Description, TSG-RAN#7, submitted as RP-000127rev
[4] UMTS 25.413: "3rd Generation Partnership Project (3GPP) Technical Specification Radio Access Network; UTRAN Iu interface RANAP signalling".
[5] UMTS 21.905: "3rd Generation Partnership Project (3GPP) Technical Specification Services and System Aspects; Vocabulary for 3GPP specifications".
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
3 Definitions, symbols and abbreviations
| |
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply.
SRNS relocation: The definition of [5] applies.
Handover: The definition of [5] applies.
Hard handover: The definition of [5] applies.
Relocation, or Relocation of SRNS: The definition of [4] applies.
Bi-casting: The capability of a node to receive original data, and send this data in its original form over two different paths.
Duplication: The capability of a node to receive original data, and send this data over one path in its original form, as well as duplicating it and sending it in a different form over a different path. The duplicated data is in a different form than the original data received.
RNC: When the procedures described in this document are applied in a GERAN context, the functions described as being part of an RNC, are part of a BSS. Therefore in this document, “RNC” should be understood as “RNC/BSS”.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
3.2 Symbols
|
None.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
3.3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply:
DL Downlink
GGSN Gateway GPRS Support Node
GTP GPRS Tunnelling Protocol
N-PDU Network PDU
PDCP Packet Data Convergence Protocol
PDU Protocol Data Unit
RLC Radio Link Protocol
RNC Radio Network Controller
RRC Radio Resource Control
SGSN Serving GPRS Support Node
UE User Equipment
UL Uplink
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
4 GSM and UMTS R99 status
|
None.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
4.1 GSM solution
|
Inter-BSC handovers in GSM are described in ref. [1].
The 2G systems have been optimised to minimize the interruption of speech during handovers. In DL the standards allow bi-casting from the MSC. In UL this is achieved by fast radio resynchronisation by the UE. Typical values are in the range of 60 to 120 ms in UL.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
4.2 UMTS R99 status
|
Relocation in UMTS R99 for the CS domain is described in ref. [1].
Similarly to the GSM solution, the interruption of speech during relocation has been minimised. In DL the standards allow bi-casting from the MSC. In UL this is achieved by fast radio resynchronisation by the UE.
In UMTS R99, relocation for the PS domain is described in ref. [2].
It only specifies lossless relocation for non real-time services with high reliability.
The basic principle of the release 99 data forwarding is described as follows:
1) At a given point of time before execution of Relocation of SRNS, source RNC stops to transmit DL data to UE,
2) Source RNC starts to forward to the target RNC, via an GTP tunnel between the RNCs, all the GTP-PDUs which were not transmitted to UE and which continue to arrive from source SGSN to source RNC.
3) Source RNC should store all forwarded data also within source RNC, which ensures lossless operation in Relocation of SRNS failure cases.
4) Target RNC stores all GTP data forwarded from source RNC and when Serving RNC operation is started, target RNC starts the DL data transmission from the first forwarded GTP-PDU.
The R99 mechanism was originally designed for non-real-time services. The principle is that the N-PDUs are forwarded from the source RNC buffers to the target RNC. Data buffering is not adapted to real-time services, and means that interruption may exceed the requirement for real-time services.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
5 Requirements
|
None.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
5.1 General
|
General requirement is to minimise disruption to the user.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
5.2 Packet loss
|
Frame loss can already occur over the radio. Therefore when relocation occurs, any frame loss happens in addition to the frames lost over the radio. Therefore frame loss should be minimised. As a reference, in CS wireless speech, the FER must not be greater than 1%.
The packet loss should be similar to what is achieved currently in 2G systems for CS wireless speech, or smaller.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
5.3 Round-trip delay
|
- The round-trip delay should be minimised in real-time conversational services.
- The round-trip delay should be similar to what is achieved currently in 2G systems for CS wireless speech, or smaller.
- The global delay variation should be minimised.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
5.4 Speech interruption
|
The speech interruption should be similar to what is achieved currently in 2G systems for CS wireless speech, or smaller.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
5.5 Frequency of interruption
|
The number and frequency of interruption perceived by the user should be minimised.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
5.6 Security
|
Editor’s Note: This section is intended to list any security requirements for the real-time handover solution.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
5.7 Inter-system operation
|
It is required that the real-time relocation solution for PS domain works with a rel4 Core Network and a GERAN. The assumption is that the GERAN will be connected to the rel4 Core Network via the Iu-PS.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
5.8 Backwards compatibility
|
The real-time relocation solution shall be backwards compatible with UMTS R99 UEs.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
5.9 General applicability of the selected solution
|
It is required, that a unique solution will be finally selected supporting
- hard handover (“UE involved”)
- SRNS Relocation (“UE not involved”)
- inter-system operation (GERAN<->UTRAN) and
- intra-system operation (GERAN, UTRAN).
The solution shall, additionally, take care of an optimum support for intra-SGSN relocation as well as for the inter-SGSN case.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
5.10 Alignment of selected solution with transport mechanisms within Rel4 CN
|
It is required that the selected solution takes into consideration transport mechanisms selected for the Rel4 PS CN.
If the Rel4 transport protocols for the PS domain utilises/requires resource reservation or initialisation of transport characteristics (like is done in CS domain), it shall be ensured that these mechanisms / initialisations / set-up are performed prior to the execution of relocation, as subsequent, delayed bearer setup [Note: whatever “bearer setup” will be called in an Rel4 PS domain] would cause an additional recognisable delay on the overall relocation process, which should be avoided.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
5.11 Support for multiple simultaneous RABs with different QoS
|
It shall be capable to relocate/handover multiple RABs belonging to the same UE with the same signalling transaction on the Iu interface. These RABs, including the RAB for call control signalling, may belong to different QoS classes, and some of them may require lossless relocation/handover.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
6 Study areas
| |
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
6.1 Solution 1: Reuse of release 99 Packet Duplication mechanism
| |
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
6.1.1 General
|
The idea of Solution 1 is to reuse the release 99 Data forwarding mechanism also for real time services requiring seamless Relocation of SRNS. Seamless Relocation of SRNS means that the interruptions to the data stream flow are minimised and are basically unnoticeable by the users.
The basic principle of SRNC duplication mechanism would be as follows:
1) At a given point of time before execution of Relocation, source RNC starts to duplicate DL GTP-PDUs: one copy is sent to local PDCP/RLC/MAC, and the other copy is forwarded to the target RNC.
2) Source RNC continues processing and sending DL data normally towards the UE.
3) Target RNC discards all forwarded GTP-PDUs arriving to target RNC until Serving RNC operation is started.
4) When target RNC takes over the serving RNC role, it starts to process the arriving DL GTP-PDUs and send DL data to the UE.
Figure 1: Packet flows during relocation, solution 1
The uplink flow is routed as in R99. The only addition compared to R99 solution is that the source RNC would, during an interim state, duplicate downlink flow to both the UE directly and to the forwarding tunnel.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
6.1.2 The main steps of Relocation for data forwarding
|
[Note: Since for the solution 1 the procedures and mechanisms of performing Relocation of SRNS for all RABs from PS domain are the same, both the handling of lossless and Seamless RABs during Relocation of SRNS are described in this chapter.]
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
6.1.2.1 Preparation of Relocation of SRNS and Resource allocation
|
In this phase the UTRAN reserves resources for the relocation.
Specifically for Solution 1, it is assumed that lossless and seamless existing RABs are set to be "subject to data forwarding" in Relocation Command.
At the end of the preparation phase source RNC should:
- for lossless RABs; stop processing DL GTP-PDUs data
- for seamless RABs; continue to process and transmit DL data normally towards UE
- for lossless and seamless RABs; start duplicating all arrived and not acknowledged & arriving DL GTP-PDUs towards target RNC
- for lossless RABs; store all buffered & arriving DL GTP-PDUs
When data forwarding is started, target RNC should:
- for lossless RABs; store all arriving DL GTP-PDUs
- for seamless RABs: discard all arriving DL GTP-PDUs
Figure 2: Control Plane - Preparation of Relocation of SRNS and Resource allocation phase
Figure 3: User Plane - Preparation of Relocation of SRNS and Resource allocation (SRNS Relocation)
Figure 4: User Plane - Preparation of Relocation of SRNS and Resource allocation (Hard Handover)
1.1.1.1 Moving the Serving RNC role to target RNC
When source RNC is ready for Relocation of SRNS Execution, it issues the SRNS Relocation Commit or commands the UE to make Hard Handover by appropriate Radio interface procedure.
For lossless RABs source RNC should forward the Sequence number information to target RNC as defined in Release 99.
After the reception of Relocation Commit from Iur, or when UEs access to target RL is detected by target RNC, target RNC takes over the Serving RNC role.
At this point of time target RNC should:
for all lossless and seamless RABs; start UL reception of data and start transmission of UL GTP-PDUs towards CN via the new GTP tunnels. The radio interface protocols may need to be reset in order to start radio interface reception.
- for seamless RABs; start processing the arriving DL GTP-PDUs and start DL transmission towards the UE. The radio interface protocols may need to be reset in order to start radio interface transmission.
for lossless RABs: start processing the buffered and arriving DL GTP-PDUs and start DL transmission towards UE. The radio interface protocols are reset as specified for Release 99 by R2.
Figure 5: Control Plane - Moving the Serving RNC role to target RNC
Figure 6: User Plane - Moving the Serving RNC role to target RNC (SRNS Relocation)
Figure 7: User Plane - Moving the Serving RNC role to target RNC (Hard Handover)
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
6.1.2.3 Switching of DL flow in CN and Completion
|
In this phase, the DL GTP tunnel is updated between the SGSN and the GGSN so that the DL flow can use the new route.
The mechanism shown assumes that the DL GTP port used for a given RAB in target RNC is the same for all arriving GTP-PDUs regardless of their arrival route.
Only effect to the UTRAN may be the slightly earlier arrival time of DL-GTP PDUs from SGSN to target RNC. This is handled, as normal arrival time variation, by user plane buffering mechanisms existing in RNC. The additional buffering can be utilised and gradually reduced when the UE moves further from the new serving RNC and the Iur+Iub delays thus increase.
Figure 8: Control Plane - Switching of DL flow in CN phase
Figure 9: User Plane - Switching of DL flow in CN
The forwarding tunnel(s) is released with timer supervision as in R99.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
6.1.3 Specifications Impact
| |
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
6.1.3.1 Impacts on RAN3 specifications
|
The Solution 1 reuses the Release 99 data forwarding mechanisms also for the seamless RABs from PS domain. Solution 1 does not require any new procedures, messages nor information elements to be introduced to any RAN 3 specification.
In R99, there is a clear indication in the RAB parameters used at RAB assignment that a RAB is to be treated in a “lossless” or “other” way. Therefore a new value for that Information Element is needed to indicate “seamless” to the source RNC.
When specifying the release 99 RANAP it was decided by RAN3 to not specify the handling of user plane in application part specifications. This was decided to keep complete independence of user and control plane handling from the stage 3 specification point of view. This independence should be preserved, and the handling of the control and user plane should be specified in appropriate stage 2 specifications (23.060).
RANAP specification should be updated to include a new value "real-time" for the Relocation Requirement IE, and a reference to 23.060 for the User Plane Handling in each case.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
6.1.3.2 Impacts on other groups’ specifications
|
Depending on RAN 2 opinion, maybe addition of one parameter to RRC container could ensure the unambiguous operation of the solution 1. (See the chapter describing the Open Issues).
Stage 2 specification TS 23.060 has to be aligned with the selected solution for RT PS domain Relocation of SRNS. The consistent handling of User Plane and Control Plane together is a matter for stage 2 specifications. The following information should be included, in the form that is most appropriate:
After Relocation Preparation is successfully terminated and before Relocation of SRNS execution is triggered the Source RNC should:
- for lossless RABs; stop processing DL GTP-PDUs data
- for seamless RABs; continue to process and transmit DL data normally towards UE
- for lossless and seamless RABs; start duplicating all arrived and not acknowledged & arriving DL GTP-PDUs towards target RNC
- for lossless RABs; store all buffered & arriving DL GTP-PDUs
After Relocation Resource Allocation procedure is successfully terminated but the serving RNC role is not yet taken over by target RNC and when DL user plane data starts to arrive to target RNC the target RNC should:
- for lossless RABs; store all arriving DL GTP-PDUs
- for seamless RABs: discard all arriving DL GTP-PDUs
When triggering the execution of Relocation of SRNS, source RNC should forward the Sequence number information to target RNC for all lossless RABs as defined in Release 99.
After reception of Relocation Commit from Iur, or in UE involved case when UEs access to target cell is detected by target RNC, target RNC takes over the Serving RNC role.
At this point of time the new Serving RNC should:
- for all lossless and seamless RABs; start UL reception of data and start transmission of UL GTP-PDUs towards CN via the new GTP tunnels. The radio interface protocols may need to be reset in order to start air interface reception.
- for seamless RABs; start processing the arriving DL GTP-PDUs and start DL transmission towards the UE. The radio interface protocols may need to be reset in order to start air interface transmission.
- for lossless RABs: start processing the buffered and arriving DL GTP-PDUs and start DL transmission towards UE. The radio interface protocols are reset as specified for Release 99 by RAN2.
No other impacts to any 3GPP specification in any other 3GPP groups are seen.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
6.1.4 Interaction with other systems
|
This section is intended to explain how this solution will work with other systems such as GERAN, UTRAN R99, GSM and GPRS. This is subject to information availability for these other systems.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
6.1.5 Summary: solution 1
|
This solution is based on making some procedure enhancements to the R99 mechanisms. During an interim state, the processing of the real time data is done at the source RNC so that the source RNC both sends the traffic to the UE, and forwards it to the target RNC.
This solution also assumes that considering the nature of RT services, there is no need to buffer any DL or UL traffic in the involved nodes.
The Solution 1 reuses the Release 99 data forwarding mechanisms also for the seamless RABs from PS domain. Solution 1 does not require any new procedures, messages nor information elements to be introduced to any RAN 3 specification.
In any relocation case (all scenarios described in 5.9), for DL data of seamless RABs there are two possible situations when frame gap or overlapping may happen:
1. The frame overlap/gap may be introduced when target RNC takes the Serving RNC role and starts to produce the DL data from forwarded GTP-PDUs. In this case the estimated gap/overlap is equal to:
- For SRNS relocation: the delay difference between the transport bearer used for Iur DCH data stream and the transport bearer used for data forwarding GTP tunnel both of which are setup between the same source and target RNCs.
- For hard handover: the delay of the GTP tunnel used for data forwarding. This first instance of frame overlap coincides with radio hard handover.
If the transport bearer delay difference is smaller than the air interface Transmission Time Interval (TTI) (10, 20, 40 or 80 ms depending on the service) the amount of gap/overlap is most likely non existent.
2. The additional frame gap may be introduced when the CN transport is optimised. In this case the gap will exist only if the delay via the optimised route is larger than the delay via the forwarding route.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
6.1.6 Open issues
|
None.
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
6.2 Solution 2: Core Network bi-casting
| |
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
6.2.1 General
|
The Core Network bi-casting mechanism handles real-time data from the GGSN/SGSN based on the model from GSM and the CS domain in UMTS R99.
The principle is that the packet anchor is at the GGSN/SGSN which acts as the equivalent of the three-party bridge in the CS domain MSC.
During the relocation, real-time downlink N-PDUs are duplicated at the GGSN and sent to the source RNC as well as to the target RNC. Additionally, at the moment the target RNC takes the role of serving RNC, it immediately begins sending uplink N-PDUs towards GGSN via the new SGSN.
The uplink flow is routed as in R99.
Figure 10: Packet flows during relocation, solution 2
|
7d3783c93dcb97023753560f1c6e0f1f
|
25.936
|
6.2.2 Relocation involving 2 SGSNs
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.