hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
1cc4b09fd057c9a5cf925fb9b5a5f4e7 | 25.945 | 8.5.3.3 Multipath fading Case 3 | |
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... |
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 (subsequ... |
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... |
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 bur... |
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 i... |
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 co... |
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... |
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 recei... |
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.... |
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 ... |
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 ... |
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... |
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
(... |
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 aver... |
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... |
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.
Figur... |
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 u... |
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
10... |
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”... |
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]
Paramete... |
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 chan... |
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 M... |
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 us... |
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.
• Fo... |
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 no... |
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... |
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 domai... |
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... |
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 relocati... |
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 mechani... |
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 duplicati... |
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 dat... |
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 e... |
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 ... |
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 o... |
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 o... |
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-... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.