i-hspa layering strategy zain sa

44
1 © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010 For internal use I-BTS Sharing two layer deployment - F1 for Rel99 and F2 for HSPA

Upload: mohammedraziuddinakheel

Post on 09-Nov-2015

13 views

Category:

Documents


4 download

DESCRIPTION

I-hspa LAYERING.

TRANSCRIPT

I-BTS Sharing two layer deployment - F1 for Rel99 and F2 for HSPA For internal use
- F1 for Rel99 and F2 for HSPA
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
One Flexi system module per site.
Flexi is connected to I-HSPA Adapter which is connected to RNC via Iur.
I-BTS Sharing in use.
F1 3G preferred for R99 traffic (AMR and Rel.99 PS).
F2 I-HSPA preferred for HSPA traffic. This frequency should be as clear as possible of R99 traffic to guarantee max HSPA throughput.
3G network also available for ISHO.
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
Intra I-ADA Softer Handover, ADJS
I-ADA
3G F2
Only F1 cells are allowed to handover to 3G layer.
DRRC/HSCAHO
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
HSDPA must always be enabled in both frequencies of I-BTS.
HSUPA can be disabled in F1 because the UEs with HSxPA are handed over immediately to F2.
Directed RRC connection setup and HSPA Layering for UEs in Common Channels features are not supported by ADA but handover and idle mode reselection based layering is used.
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
Cell Reselection strategy
To avoid CS calls in F2, NRT HOPI and WCEL parameters in ADA F2 cells shall be used to force UEs in idle or PCH to always reselect F2->F1.
For F2 cells set NRT HOPI->AdjiQoffset2=-15 (-15 dB).
For F2 cells set WCEL->QqualMin=-11 (-11 dB).
For F2 cells set WCEL->Sintersearch=9 (18 dB).
In practise it is seen that some UEs reselect to F1 also in FACH.
Reselection F1->F2 shall not be allowed in any state.
Set F1 NRT HOPI and NRT HOPI AdjiQoffset2 to maximum value 50 dB.
Because most of CS calls start from idle, most of CS traffic will be in F1 as UEs on idle will be there.
Its recommended to set IADA->UL_DL_activation_timer=10 to prevent too fast transition from FACH to PCH.
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
Target:
Move user from F1 to F2 because that is preferred for HSPA.
Scenario:
RRC connection established on F1.
RAB assignment and HSDPA allocation of F1. ADA remains SRNC.
HSDPA FMCS HHO trigger shall be set to extreme value so that intra-ADA IFHO F1->F2 ”coverage handover” is triggered immediately and call continues on F2.
(ADA feature: ARAN1276 HSDPA Inter-frequency Handover)
When the UE goes to PCH, it reselects to F1.
F1/ADA
1
3
2
F2/ADA
F2/RNC
F1/RNC
ADA/ADJI
ADA/ADJI
4
For internal use
F1/ADA
HSDPA user plane allocation (ADA)
HSDPA IFHO to F2 (ADA)
Transition to PCH state or RRC connection released, cell reselection to F1.
1
3
2
F2/ADA
F2/RNC
F1/RNC
ADA/ADJI
ADA/ADJI
4
For internal use
- parameters
Enable license for ARAN1276 feature, WBTS->BTSSupportForHSPACM=1, WCEL->HSDPAFmciIdentifier to non-zero value
Disable HSUPA in F1 because IFHO requires anyway immediate downgrading to HSDPA due to compressed mode measurements. After IFHO, HSUPA can be immediately allocated on F2.
Define different FMCS and FMCI objects for F1 and F2 cells (HSDPAFmcsIdentifier, HSDPAFmciIdentifier)
HSDPA FMCS for F1 cell (triggers always immediate handover)
HHoRscpThreshold=-28 dBm
HHoRscpCancel = -25 dBm
IFHOcauseCPICHrscp=1
F1 HOPI->ADJIMinRSCP default value can be used.
F1 HOPI->AdjiEcNoMargin=-24 dB (plan value -48) can be used to trigger IFHO even if EcNo in F2 would be worse than in F1.
In F2->FMCI parameters all IFHO causes disabled.
See slide ”Cell Reselection strategy” about FMCI parameters.
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
Scenario 2: CS Voice call setup on F1 from idle
Target:
Make CS voice call on F1 and also stay on F1.
Scenario:
RRC connection established on F1.
I-BTS sharing handover to RNC, CS voice call continues on F1 with RNC as SRNC and ADA as DRNC.
-> Nothing special, this is basic I-BTS Sharing functionality
F1/ADA
1
2
F2/ADA
F2/RNC
F1/RNC
For internal use
Scenario 2: CS Voice call setup on F1 from idle
F1/ADA
1
2
F2/ADA
F2/RNC
F1/RNC
For internal use
Scenario 3: CS Voice call setup on F2
If the user for some reason gets to make CS call on F2, the call is kept there but later in idle mode the UE is moved to F1.
Scenario:
UE camped on F2 (e.g. due to active PS call) and makes CS voice call.
RRC connection established on F2.
I-BTS sharing handover to RNC, CS voice call established on F2 with RNC as SRNC and ADA as DRNC.
CS call continues on F2 as long until RRC connection is released (means both CS and PS). After that idle mode cell reselection to F1.
F1/ADA
1
2
3
F2/ADA
F2/RNC
F1/RNC
ADA/ADJI
ADA/ADJI
For internal use
Scenario 3: CS Voice call setup on F2 from idle
F1/ADA
Relocation due to CS (ADA->RNC), call continues on F2
When RRC connection is released and UE goes to idle, it makes idle mode reselection to F1.
1
2
3
F2/ADA
F2/RNC
F1/RNC
ADA/ADJI
ADA/ADJI
For internal use
- parameters
Service and Load Based Handover feature is not supported during anchoring. Thus if CS call is setup on F2, it continues there.
HOPI for F2 cells in ADA shall be configured with such parameters that idle mode reselection F2->F1 happens always when the UE is in idle (SIB11). (see slide Cell Reselection strategy)
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
- with R99 PS support in ADA (ADA2.0 P8)
Target:
Scenario:
Non-HSDPA UE is camped to F1 or F2.
UE makes PS call, ADA accepts the connection.
RAB is established and Rel99 PS data transfer starts with ADA as serving-RNC.
F1/ADA
1
3
F2/ADA
F2/RNC
F1/RNC
2
2G
For internal use
- with R99 PS support in ADA (ADA2.0 P8)
F1/ADA
1
3
F2/ADA
F2/RNC
F1/RNC
2
2G
For internal use
Scenario 5: Inter-ADA soft mobility
ADJS shall be defined between all adjacent ADA cells in both frequencies.
Iur interfaces shall be configured between adjacent ADAs.
CS call handovers executed by the RNC utilize these same ADJS definitions found in ADA RNW-database.
ADA-1/F2
ADA-1/F1
ADA-2/F2
ADA-2/F1
ADJS
ADJS
ADJS
ADJS
For internal use
- F1 preferred for CS, F2 for PS
2G
Note: Iur-interface needed between ADAs.
Adjacencies defined in Rel2 ADA:
1) Used for Cell_PCH and Idle cell reselection from F2. Needed to achieve F1=Rel99, F2=PS preferred configuration. Not used for connected mode handovers.
2) Used for PS call IFHO from F1 to F2 for achieving F1=Rel99, F2=PS preferred configuration.
3) Inter-ADA SHO for CS and PS calls on F2
4) Inter-ADA SHO for CS and PS calls on F1
5) Coverage ISHO from F2 to 2G for CS calls. Also CS calls can exist on F2, at least during Multi-RAB.
6) Coverage ISHO from F1 to 2G for CS calls.
NOTE 1:
Iur interface is needed between ADAs because inter-BTS ADJS have been defined in ADA RNW database as they are definitely needed to enable CS call mobility. When ADJS exists, then UEs will report 1A branch addition events for that. This triggers handover attempt and if Iur-interface does not exist, SHO cannot be done and ADA triggers intra-ADA HHO which is not good from service quality point of view.
However CS calls controlled by the RNC do not utilize Iur between ADAs, but only Iur between ADA and RNC.
NOTE 2:
In I-BTS Sharing sites, all ADJx are defined in ADA RNW database, not in RNC DB. RNC gets the adjacency information from ADA in RNSAP Radio Link Setup Response and Addition Response messages.
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
Adjacencies defined in Rel2 ADA:
1) Used for Cell_PCH and Idle cell reselection from F2. Needed to achieve F1=Rel99, F2=PS preferred configuration. Not used for connected mode handovers.
2) Used for PS call IFHO from F1 to F2 for achieving F1=Rel99, F2=PS preferred configuration.
3) Inter-ADA SHO for CS and PS calls on F2
4) Inter-ADA SHO for CS and PS calls on F1
5) Coverage ISHO from F2 to 2G for CS calls. Also CS calls can exist on F2, at least during Multi-RAB.
6) Coverage ISHO from F1 to 2G for CS calls.
NOTE 1:
Iur interface is needed between ADAs because inter-BTS ADJS have been defined in ADA RNW database as they are definitely needed to enable CS call mobility. When ADJS exists, then UEs will report 1A branch addition events for that. This triggers handover attempt and if Iur-interface does not exist, SHO cannot be done and ADA triggers intra-ADA HHO which is not good from service quality point of view.
However CS calls controlled by the RNC do not utilize Iur between ADAs, but only Iur between ADA and RNC.
NOTE 2:
In I-BTS Sharing sites, all ADJx are defined in ADA RNW database, not in RNC DB. RNC gets the adjacency information from ADA in RNSAP Radio Link Setup Response and Addition Response messages.
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
- F1 preferred for CS, F2 for PS
2G
Adjacencies defined in RNC RNW DB:
Used for coverage based handover between F1 and F2. (Note: There can also be ADJI from RNC to ADA if wanted)
2) ISHO from RNC cells to 2G
3) ADJS from RNC-cell to I-BTS cell
Adjacencies defined in ADA RNW DB:
4) ADJS from I-BTS cell to RNC-cell
5) ISHO from I-BTS cell to 2G
6) Used for Cell_PCH and Idle cell reselection from F2. Needed to achieve F1=Rel99, F2=PS preferred configuration. Not used for connected mode handovers.
7) Used for PS call IFHO from F1 to F2 for achieving F1=Rel99, F2=PS preferred configuration.
NOTE:
In I-BTS Sharing sites, all ADJx are defined in ADA RNW database, not in RNC DB. RNC gets the adjacency information from ADA in RNSAP Radio Link Setup Response and Addition Response messages.
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
- F1 preferred for CS, F2 for PS
Adjacencies defined in RNC RNW DB:
Used for coverage based handover between F1 and F2. (Note: There can also be ADJI from RNC to ADA if wanted)
2) ISHO from RNC cells to 2G
3) ADJS from RNC-cell to I-BTS cell
Adjacencies defined in ADA RNW DB:
4) ADJS from I-BTS cell to RNC-cell
5) ISHO from I-BTS cell to 2G
6) Used for Cell_PCH and Idle cell reselection from F2. Needed to achieve F1=Rel99, F2=PS preferred configuration. Not used for connected mode handovers.
7) Used for PS call IFHO from F1 to F2 for achieving F1=Rel99, F2=PS preferred configuration.
NOTE:
In I-BTS Sharing sites, all ADJx are defined in ADA RNW database, not in RNC DB. RNC gets the adjacency information from ADA in RNSAP Radio Link Setup Response and Addition Response messages.
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
CS call ISHO to 3G
ADJI for coverage based ISHO to 3G shall be defined both for F1 and F2 cells in ADA. RNC gets the neighbour information via RNSAP messages.
Set RNC->ISHOInIurMobility=1 to enable ISHO from anchoring.
Define HOPI and FMCI objects in the RNC to be used during anchoring and attach them to VCEL object.
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
Other considerations
Set RNC->DCHScheOverIur=1 to enable PS NRT scheduling during anchoring and thus >64 kbps bitrates for CS+PS multi-RABs.
When integrating a new site to the network, the layering features could be first disabled until basic functionality is verified. After the site is stable, then activate layering to get load balancing working.
Different multi-RAB scenarios must be verified in testing, like AMR+PS and PS+AMR.
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
One Flexi system module per site.
Flexi is connected to I-HSPA Adapter which is connected to RNC via Iur.
I-BTS Sharing in use.
F1 preferred for R99 traffic (AMR and Rel.99 PS).
F2 preferred for HSPA traffic. This frequency should be as clear as possible of R99 traffic to guarantee max HSPA throughput.
3G network available for ISHO.
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
Intra I-ADA Softer Handover, ADJS
I-ADA
3G F2
Only F1 cells are allowed to handover to 3G layer.
DRRC/HSCAHO
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
HSDPA must always be enabled in both frequencies of I-BTS.
HSUPA can be disabled in F1 because the UEs with HSxPA are handed over immediately to F2.
Directed RRC connection setup and HSPA Layering for UEs in Common Channels features are not supported by ADA but handover and idle mode reselection based layering is used.
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
Cell Reselection strategy
To avoid CS calls in F2, NRT HOPI and WCEL parameters in ADA F2 cells shall be used to force UEs in idle or PCH to always reselect F2->F1.
For F2 cells set NRT HOPI->AdjiQoffset2=-15 (-15 dB).
For F2 cells set WCEL->QqualMin=-11 (-11 dB).
For F2 cells set WCEL->Sintersearch=9 (18 dB).
In practise it is seen that some UEs reselect to F1 also in FACH.
Reselection F1->F2 shall not be allowed in any state.
Set F1 NRT HOPI and NRT HOPI AdjiQoffset2 to maximum value 50 dB.
Because most of CS calls start from idle, most of CS traffic will be in F1 as UEs on idle will be there.
Its recommended to set IADA->UL_DL_activation_timer=10 to prevent too fast transition from FACH to PCH.
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
Target:
Move user from F1 to F2 because that is preferred for HSPA.
Scenario:
RRC connection established on F1.
RAB assignment and HSDPA allocation of F1. ADA remains SRNC.
HSDPA FMCS HHO trigger shall be set to extreme value so that intra-ADA IFHO F1->F2 ”coverage handover” is triggered immediately and call continues on F2.
(ADA feature: ARAN1276 HSDPA Inter-frequency Handover)
When the UE goes to PCH, it reselects to F1.
F1/ADA
1
3
2
F2/ADA
F2/RNC
F1/RNC
ADA/ADJI
ADA/ADJI
4
For internal use
F1/ADA
HSDPA user plane allocation (ADA)
HSDPA IFHO to F2 (ADA)
Transition to PCH state or RRC connection released, cell reselection to F1.
1
3
2
F2/ADA
F2/RNC
F1/RNC
ADA/ADJI
ADA/ADJI
4
For internal use
- parameters
Enable license for ARAN1276 feature, WBTS->BTSSupportForHSPACM=1, WCEL->HSDPAFmciIdentifier to non-zero value
Disable HSUPA in F1 because IFHO requires anyway immediate downgrading to HSDPA due to compressed mode measurements. After IFHO, HSUPA can be immediately allocated on F2.
Define different FMCS and FMCI objects for F1 and F2 cells (HSDPAFmcsIdentifier, HSDPAFmciIdentifier)
HSDPA FMCS for F1 cell (triggers always immediate handover)
HHoRscpThreshold=-28 dBm
HHoRscpCancel = -25 dBm
IFHOcauseCPICHrscp=1
F1 HOPI->ADJIMinRSCP default value can be used.
F1 HOPI->AdjiEcNoMargin=-24 dB (plan value -48) can be used to trigger IFHO even if EcNo in F2 would be worse than in F1.
In F2->FMCI parameters all IFHO causes disabled.
See slide ”Cell Reselection strategy” about FMCI parameters.
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
Scenario 2: CS Voice call setup on F1 from idle
Target:
Make CS voice call on F1 and also stay on F1.
Scenario:
RRC connection established on F1.
I-BTS sharing handover to RNC, CS voice call continues on F1 with RNC as SRNC and ADA as DRNC.
-> Nothing special, this is basic I-BTS Sharing functionality
F1/ADA
1
2
F2/ADA
F2/RNC
F1/RNC
For internal use
Scenario 2: CS Voice call setup on F1 from idle
F1/ADA
1
2
F2/ADA
F2/RNC
F1/RNC
For internal use
Scenario 3: CS Voice call setup on F2
If the user for some reason gets to make CS call on F2, the call is kept there but later in idle mode the UE is moved to F1.
Scenario:
UE camped on F2 (e.g. due to active PS call) and makes CS voice call.
RRC connection established on F2.
I-BTS sharing handover to RNC, CS voice call established on F2 with RNC as SRNC and ADA as DRNC.
CS call continues on F2 as long until RRC connection is released (means both CS and PS). After that idle mode cell reselection to F1.
F1/ADA
1
2
3
F2/ADA
F2/RNC
F1/RNC
ADA/ADJI
ADA/ADJI
For internal use
Scenario 3: CS Voice call setup on F2 from idle
F1/ADA
Relocation due to CS (ADA->RNC), call continues on F2
When RRC connection is released and UE goes to idle, it makes idle mode reselection to F1.
1
2
3
F2/ADA
F2/RNC
F1/RNC
ADA/ADJI
ADA/ADJI
For internal use
- parameters
Service and Load Based Handover feature is not supported during anchoring. Thus if CS call is setup on F2, it continues there.
HOPI for F2 cells in ADA shall be configured with such parameters that idle mode reselection F2->F1 happens always when the UE is in idle (SIB11). (see slide Cell Reselection strategy)
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
- with R99 PS support in ADA (ADA2.0 P8)
Target:
Scenario:
Non-HSDPA UE is camped to F1 or F2.
UE makes PS call, ADA accepts the connection.
RAB is established and Rel99 PS data transfer starts with ADA as serving-RNC.
F1/ADA
1
3
F2/ADA
F2/RNC
F1/RNC
2
2G
For internal use
- with R99 PS support in ADA (ADA2.0 P8)
F1/ADA
1
3
F2/ADA
F2/RNC
F1/RNC
2
2G
For internal use
Scenario 5: Inter-ADA soft mobility
ADJS shall be defined between all adjacent ADA cells in both frequencies.
Iur interfaces shall be configured between adjacent ADAs.
CS call handovers executed by the RNC utilize these same ADJS definitions found in ADA RNW-database.
ADA-1/F2
ADA-1/F1
ADA-2/F2
ADA-2/F1
ADJS
ADJS
ADJS
ADJS
For internal use
- F1 preferred for CS, F2 for PS
2G
Note: Iur-interface needed between ADAs.
Adjacencies defined in Rel2 ADA:
1) Used for Cell_PCH and Idle cell reselection from F2. Needed to achieve F1=Rel99, F2=PS preferred configuration. Not used for connected mode handovers.
2) Used for PS call IFHO from F1 to F2 for achieving F1=Rel99, F2=PS preferred configuration.
3) Inter-ADA SHO for CS and PS calls on F2
4) Inter-ADA SHO for CS and PS calls on F1
5) Coverage ISHO from F2 to 2G for CS calls. Also CS calls can exist on F2, at least during Multi-RAB.
6) Coverage ISHO from F1 to 2G for CS calls.
NOTE 1:
Iur interface is needed between ADAs because inter-BTS ADJS have been defined in ADA RNW database as they are definitely needed to enable CS call mobility. When ADJS exists, then UEs will report 1A branch addition events for that. This triggers handover attempt and if Iur-interface does not exist, SHO cannot be done and ADA triggers intra-ADA HHO which is not good from service quality point of view.
However CS calls controlled by the RNC do not utilize Iur between ADAs, but only Iur between ADA and RNC.
NOTE 2:
In I-BTS Sharing sites, all ADJx are defined in ADA RNW database, not in RNC DB. RNC gets the adjacency information from ADA in RNSAP Radio Link Setup Response and Addition Response messages.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
Adjacencies defined in Rel2 ADA:
1) Used for Cell_PCH and Idle cell reselection from F2. Needed to achieve F1=Rel99, F2=PS preferred configuration. Not used for connected mode handovers.
2) Used for PS call IFHO from F1 to F2 for achieving F1=Rel99, F2=PS preferred configuration.
3) Inter-ADA SHO for CS and PS calls on F2
4) Inter-ADA SHO for CS and PS calls on F1
5) Coverage ISHO from F2 to 2G for CS calls. Also CS calls can exist on F2, at least during Multi-RAB.
6) Coverage ISHO from F1 to 2G for CS calls.
NOTE 1:
Iur interface is needed between ADAs because inter-BTS ADJS have been defined in ADA RNW database as they are definitely needed to enable CS call mobility. When ADJS exists, then UEs will report 1A branch addition events for that. This triggers handover attempt and if Iur-interface does not exist, SHO cannot be done and ADA triggers intra-ADA HHO which is not good from service quality point of view.
However CS calls controlled by the RNC do not utilize Iur between ADAs, but only Iur between ADA and RNC.
NOTE 2:
In I-BTS Sharing sites, all ADJx are defined in ADA RNW database, not in RNC DB. RNC gets the adjacency information from ADA in RNSAP Radio Link Setup Response and Addition Response messages.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
- F1 preferred for CS, F2 for PS
2G
Adjacencies defined in RNC RNW DB:
Used for coverage based handover between F1 and F2. (Note: There can also be ADJI from RNC to ADA if wanted)
2) ISHO from RNC cells to 2G
3) ADJS from RNC-cell to I-BTS cell
Adjacencies defined in ADA RNW DB:
4) ADJS from I-BTS cell to RNC-cell
5) ISHO from I-BTS cell to 2G
6) Used for Cell_PCH and Idle cell reselection from F2. Needed to achieve F1=Rel99, F2=PS preferred configuration. Not used for connected mode handovers.
7) Used for PS call IFHO from F1 to F2 for achieving F1=Rel99, F2=PS preferred configuration.
NOTE:
In I-BTS Sharing sites, all ADJx are defined in ADA RNW database, not in RNC DB. RNC gets the adjacency information from ADA in RNSAP Radio Link Setup Response and Addition Response messages.
* © Nokia Siemens Networks Presentation / Author / Date
For internal use
- F1 preferred for CS, F2 for PS
Adjacencies defined in RNC RNW DB:
Used for coverage based handover between F1 and F2. (Note: There can also be ADJI from RNC to ADA if wanted)
2) ISHO from RNC cells to 2G
3) ADJS from RNC-cell to I-BTS cell
Adjacencies defined in ADA RNW DB:
4) ADJS from I-BTS cell to RNC-cell
5) ISHO from I-BTS cell to 2G
6) Used for Cell_PCH and Idle cell reselection from F2. Needed to achieve F1=Rel99, F2=PS preferred configuration. Not used for connected mode handovers.
7) Used for PS call IFHO from F1 to F2 for achieving F1=Rel99, F2=PS preferred configuration.
NOTE:
In I-BTS Sharing sites, all ADJx are defined in ADA RNW database, not in RNC DB. RNC gets the adjacency information from ADA in RNSAP Radio Link Setup Response and Addition Response messages.
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
CS call ISHO to 3G
ADJI for coverage based ISHO to 3G shall be defined both for F1 and F2 cells in ADA. RNC gets the neighbour information via RNSAP messages.
Set RNC->ISHOInIurMobility=1 to enable ISHO from anchoring.
Define HOPI and FMCI objects in the RNC to be used during anchoring and attach them to VCEL object.
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
Other considerations
Set RNC->DCHScheOverIur=1 to enable PS NRT scheduling during anchoring and thus >64 kbps bitrates for CS+PS multi-RABs.
When integrating a new site to the network, the layering features could be first disabled until basic functionality is verified. After the site is stable, then activate layering to get load balancing working.
Different multi-RAB scenarios must be verified in testing, like AMR+PS and PS+AMR.
* © Nokia Siemens Networks I-HSPA two layer strategy / JRa / 09.03.2010
For internal use
Other Parameter Recommendations
- PrxMaxTargetBTS = 8
- PrxTarget = 6
- PrxTargetPSMax = 6
- PrxTargetPSMin = 6
- HSDPA16KBPSReturnChannel=1
- BTSSupportForHSPACM = 1 (enable HSDPA IFHO in ADA)
- MaxNbrOfHSSCCHCodes = 3 (enable code multiplexing)