Escolar Documentos
Profissional Documentos
Cultura Documentos
Performance features
Mobility features
during soft handover, up to 126 or 189 cells, as the RNC integrates the intrafrequency neighbour cell definitions of the active set cells. The feature is based on the 3GPP feature that allows the UE to measure and report any intra-frequency cell (in addition to active and monitored set cells) which is outside the intra-frequency cell list of the UE. This capability removes the limitation on the length of the intra-frequency cell
list (32 cells) since the UE can include any detected intra-frequency cell in the event evaluation and reporting.
The RNC adds the detected cell into the active set if the detected cell is
defined as the intra-frequency neighbour cell of the active set cell.
When the feature is enabled, it is possible to define max 32 additional intra-frequency neighbour cells (new object ADJD) in addition to the max 31 intra-frequency neighbour cells (object ADJS) of the WCDMA cell. Additional intra-frequency neighbour cell definitions are used only for the identification of the detected cells. Additional intra-frequency neighbour cell may be located in any UMTS Radio Access Network (UTRAN) of any Public Land Mobile Network (PLMN). The neighbour cell parameters are defined by attaching specified HOPS parameter sets (RT, NRT, HSDPA and HSPA) to the additional intra-frequency neighbour cell.
RNC
Missing neighbors can occur in SHO if combined neighbor list is less than all neighbors of all AS cells (as a result of neighbor list combination)
handover decision process when the value is 0 (DSR is not allowed) or 1 (DSR is enabled but SHO to detected cell is not allowed). Handover control includes those detected set cells in the handover decision process (in addition to the active and monitored set cells) which are defined in the ADJS (but are left out from the full combined intra-frequency cell list) and ADJD database objects of the active set cells when the value of the parameter FMCS - DSRepBasedSHO is 2 (DSR based SHO is enabled).
Improved call completion Improved throughput per user and on system level Improved possibilities for optimisation
License requirements
Licence description Licence control in network element Licence control attributes Licence type RNC LK Long-term capacity licence (# of BTS)
Activation per cell required New measurement M1028, new counters as below No alarms Updated KPIs on SHO success New KPIs on amount of detected cell, EcNo and RSCP
10
11
12
SRNC
DRNC
NodeB
NodeB
S-Cell1 f1
S-Cell2 f2
13 Nokia Siemens Networks RU10 for Network Planners 2008 / 03.04.2008
D-Cell2 f2
Inter-RNC inter-frequency handover can be carried out over the Iur if the DRNC or CN does not support SRNS relocation Inter-frequency handover over the Iur is required when there are isolated cells, e.g. indoor cells, in some carrier under the DRNS or if some carrier has a dedicated RNC If the DRNC or CN does not support the SRNS relocation procedure, the SRNC continues as a controlling node (anchoring point) for the RRC connection when the UE moves under the DRNS The user plane traffic between the DRNC and CN is transferred via Iur and the SRNC If the intra-frequency coverage under the DRNS is not continuous, the inter-RNC interfrequency handover will be carried out over the Iur The DRNC sends information to the SRNC on the inter-frequency neigbour cells (in addition to the intra-frequency neighbour cells) that have been defined for the active set cell(s) controlled by the DRNC The SRNC takes into account the inter-RNC inter-frequency neighbour cell information in the inter-frequency measurement and handover decision procedures The SRNC has specific BTS and cell level handover control parameters, that are used during anchoring for the active set cells controlled by the DRNC and for the neighbouring cells defined on the DRNC side The SRNC and DRNC support compressed mode during the inter-frequency measurements
14
15
Activation required Follow up by measurement M1014 New KPIs on IFHO under DRNC No alarms
16
RNC
UE or RAN trigger starts ISHO .. or RAN internal event allow cancellation
17
The inter-system measurement phase takes a few seconds and during that
time the conditions in the WCDMA layer may change => Cancellation
18
Inter-System measurements may be started in the UE due to the radio coverage and connection quality (uplink DCH quality, UE TX power, downlink DPCH power, CPICH RSCP or CPICH Ec/No) reasons . When the inter-system measurements are completed, the target cell selection takes place. The inter-system measurement phase takes a few seconds and during that time the conditions in the WCDMA layer may change. During the inter-system measurements the UE measures also intra-frequency WCDMA neighbors. If the intra-frequency measurements indicate that the conditions have improved in the WCDMA layer so that defined cancellation thresholds are exceeded, the RNC stops the handover and compressed mode measurements. Also, if the UE Internal Measurements or the RL Quality measurements indicate that the radio conditions have improved, the ongoing inter-system Handover is interrupted or cancelled. Active set update due to cell addition/replacement during the measurements also causes the inter-system handover cancellation. With this feature unnecessary Inter-System Handovers can be cancelled in the UE thus retaining the call in current WCDMA network.
19
CM Required
NBAP/RNSAP: RL Reconfiguration Prepare NBAP/RNSAP: RL Reconfiguration Ready NBAP/RNSAP: RL Reconfiguration Commit RRC: Ph/ Tr Channel Reconfiguration RRC: Measurement Control (Inter-System Meas) RRC: Ph/ Tr Channel Reconfiguration Complete RRC: Measurement Report (RSSI Meas) RRC: Measurement Report (Event 1E for CPICH EcNo)
Inter-system measurement cancellation decision
M e a s u r
Stop CM
NBAP/RNSAP: RL Reconfiguration procedure or CM Command RRC Measurement Control RRC: Ph/Tr Channel Reconfiguration (Optional)
Stop CM Ack
e m e n t p h a s e
20
21
triggered by DL power New counters M1010C203-C214 per RT/NRT and trigger reasons No alarms
22
UE
23
Separate Treselection values for Cell_FACH state and for Cell_PCH/URA_PCH state and Inter-RAT Scaling Factor for Treselection Speed Dependent Scaling Factor for Treselection parameter for high Separate QHyst1 and QHyst2 values for Cell_FACH state and for
Cell_PCH/URA_PCH state are included in SIB4 mobility UEs is supported parameter are included in SIB4
24
25
No license requirements Activation per WCEL required No alarms, no counters New/related parameters as below
26
27
28
RNC Parameters
29
(Unlicensed Mobile Access), is a radio network with combined GSM and WLAN access UTRAN-GAN Interworking enables handovers for ongoing voice calls between UTRAN and GAN networks
RNC sets up the
measurement event 3a to UEs supporting handover to GAN RNC includes neighbouring GAN cell(s) in Inter-RAT Measurement Objects list
30
31
32
33
License activation with ZW7, feature code 1309 RNC and WCEL configuration is required New counter M1001C643 on RRC release due to GAN-HO New counters M1010C219-C222 on attempted, successful and unsuccessful GAN-HO No alarms, new and related parameters as below
34
35
In case the WCEL has inter-system adjacency (ADJG) to the GAN cell, but no intersystem adjacency to the GSM cell, the following WCEL parameters are not used and do not need to be configured: HSDPAFmcgIdentifier NrtFmcgIdentifier RtWithHSDPAFmcgIdentifier RtFmcgIdentifier In case the inter-system adjacency is a GAN specific ADJG, the following ADJG parameters are not used and do not need to be configured: AdjgTxPwrMaxRACH AdjgTxPwrMaxTCH NrtHopgIdentifier RtHopgIdentifier
Performance features
36
Choose this AMR codec mode set when there is high load AMR codec mode selection based on:
TX power of RT traffic: NRT traffic is downgraded first Total TX power: AMR traffic is downgraded first, then NRT and HSPA Non-HSPA TX power: AMR traffic is downgraded, if R99 NRT load is high
38
SC < Target?
No
SC < Target?
No
Yes Incoming: Select SF128 if Initial code power>Ptxmax+ AMRSF Downgrading: Select SF128 if Current code power>Ptxmax+ AMRSF
39 Nokia Siemens Networks RU10 for Network Planners 2008 / 03.04.2008
SF256
SC:= Load in Spreading code domain For the ongoing calls, the AMR codec mode change is applied gradually to avoid sudden signalling peaks caused by the Radio Link Reconfiguration procedures The AMR codec mode set {5.90, 4.75} with a 3.4 kbit/s signalling radio bearer bit rate allows the usage of SF256 in downlink instead of SF128 At the radio interface, a somewhat higher energy per bit is required for the AMR 5.9 kbps than for AMR 12.2 kbps due to difference in SF The AMR codec mode 5.9 on SF256 consumes more transmission power than AMR 5.9 on SF128. Therefore, if radio link transmitted power exceeds a predefined threshold and if a spreading code on SF128 is available, SF128 is used.
40
+120%
210
Users
With lower codec mode set: Higher radio capacity (~60%) More voice users with the same Iub and Iur transport resources (~120%) Larger spreading code space with SF256
41 Nokia Siemens Networks RU10 for Network Planners 2008 / 03.04.2008
42
43
License requirements
Licence description Licence control in network element Licence control attributes Licence type FIFILE -
RNC and WCEL configuration is required Update of existing KPIs 0014, 0015 on allocated AMR capacity New counters M1000288-C299 to follow up load situation New counters M1002C219-C222 on (re-)allocations and failures No alarms, new and related parameters as below
44
AMROverXYZ : Overload threshold for capacity area XYZ AMRTargetXYZ : Target load for capacity area XYZ AMRUnderXYZ : Underload threshold for capacity area XYZ
For power these relate the threshold to Ptxtarget
Indicator for downlink radio power load : Selects power quantity AMRSF : Influences the choice between SF128 and 256 Usage of Load based AMR codec mode selection : Enabling param.
45
T314 Timer
No coverage
UE looses coverage: BTS sends radio link failure RNC starts T314 timer UE goes to Cell_FACH state UE regains coverage: UE sends Cell Update RNC sends Cell Update Confirm, UE in Cell_DCH RNC sends RB reconfiguration UE sends RB reconf. confirm
46 Nokia Siemens Networks RU10 for Network Planners 2008 / 03.04.2008
RRC connection for AMR speech, CS data and PS streaming services is re-established after a temporary loss of RF coverage e.g. in tunnel areas The feature improves call completion ratio and thus enhances the end user experience This feature extends the support of RRC connection re-establishment procedure to CS and PS RABs of streaming or conversational classes If a UE loses the radio connection in Cell_DCH state due to loss of coverage, it moves to Cell_FACH state When the radio coverage is recovered, the UE sends a cell update message to the RNC with cause radio link failure The RNC starts the operator configurable timer T314 when it receives the radio link failure message from the BTS(s). Radio Link Failure is sent 2 seconds (not modifiable!) after WBTS has received 8 out-ofsynch indications from UL L1 If the cell update message is received from the UE before T314 has expired, the RNC moves the UE back to Cell_DCH state with cell update confirm message If T314 expires all RABs and Iu are released by RNC
47
48
predefined time window is exceeded Typically for fast moving UEs Reduces URA update signaling between the UE and RNC On the other hand paging load increases UTRAN registration areas may be overlapping Up to 8 URA identifiers can be broadcasted in one cell UE in URA_PCH state has always one valid URA The first URA ID in the URA-list of the cell is the primary URA, which is assigned to the UE in this cell The rest of the URA IDs in the URA-list are secondary URAs UE does not initiate URA update procedure in the cells where the assigned URA is included in the URA-list UE is paged in the cells where the assigned URA is in the URA-list
49 Nokia Siemens Networks RU10 for Network Planners 2008 / 03.04.2008
Cell_DCH
Cell_FACH
Idle Mode
50 Nokia Siemens Networks RU10 for Network Planners 2008 / 03.04.2008
Cell_PCH to Cell_DCH transiotion is also new in RU10: The cell update confirm (CUC) procedure can be used for direct state transition from Cell_PCH to Cell_DCH and for RRC connection re-establishment procedure. In 3GPP Rel5 Cell update message contains a new information (e.g. traffic volume measurement indication), which can be used for immediately allocate the Cell_DCH state resources to the UE.
51
52
No alarms New counters M1001C593-C594 on RAB Active Failures in PCH New counters in M1006 to count various events in PCH New counter M802C22 to count average # of users in PCH
53
CellReselectionObservingTime
will be interpreted as Fast-moving and it is switched to URA_PCH instead of Cell_PCH Default values for MaxCellReselections and CellReselectionObservingTime has been chosen by assuming that the average cell-radius in the RNC-area is e.g. 2.5km, and thus the values MaxCellReselections=3 and "CellReselextionObservingTime"=4minute will give 112 km/h as an average speed for the "Fast-moving UE" Values of MaxCellReselections and CellReselectionObservingTime need to be finetuned if there is a different (average) cell-radius used in the RNC and/or different distribution/level of mobility in the UE-population In general, all low-mobility users (at least stationary and pedestrian) should remain in Cell_PCH state to avoid unnecessary increase of the paging load
54
Both PCH states can be activated /deactivated by setting MSActivitySupervision to non zero/zero, indicating that
Cell_PCH/URA_PCH states are used/not used
55
Core Network driven feature Enables reconfiguration of RAB (attributes) This is required for service differentiation with a single Access Point Name Related CN features:
Service based QoS in QoS aware GGSN/ISN recognises service by performing IP packet
look-ups
"Service based QoS" in the NSN GGSN/ISN The feature recognises service by performing IP packet look-ups, and applies operator configurable QoS policy (service => QoS) accordingly by "GGSN initiated PDP context modification procedure" (Rel99 TS 23.060) "peer-to-peer control" in the NSN ISN The feature recognises set of peer-to-peer applications (incl. Skype) by various methods, i.e. protocol signatures and pattern recognition. The feature applies operator configurable QoS policy (service => QoS) accordingly by "GGSN initiated PDP context modification procedure" (Rel99 TS 23.060) Operators wish to use a single APN for all services but still use service differentiation Currently operators can perform service differentiation by using different APNs for different services (in this case different HLR QoS profiles are defined for each APN) This requires complex configurations and is difficult from charging point-ofview
The reconfiguration is triggered by the CN with a RAB Setup message requesting reconfiguration of the existing RAB The following RAB parameters can be changed for the interactive and background traffic class RABs: Traffic class interactive <-> background Maximum bit rate (UL/DL) Change of Traffic Handling Priority (THP) of an interactive RAB Change of Allocation and Retention Priority (ARP)
57
If applicable, new SPI and MBR values are sent from the RNC
to the NodeB and new DSCP value is taken into use in the RNC.
RU10 for Network Planners 2008 / 03.04.2008
58
59
60
License requirements
Licence description Licence type Licence control in network RNC LK element Licence control attributes Long-term ON/OFF licence
NodeBRABReconfigSupport
Further details TBD New KPIs on RAB reconfiguration success rate New counter M1001C197 on attempts New counters M1003C9,12,20,24-C222 on requests, successes and failures No alarms
61
Cells 32 32 32
62
System Information Block type 11bis (SIB11bis) provides extension segments for SIB11 and solves an inconsistency problem in 3GPP TS 25.331, which has prevented the usage of complete neighbouring cell lists for idle mode UEs System Information Block type 11/11bis: contains measurement control information to be used in the cell. This SIB is read by MSs in idle mode and in CELL_FACH, CELL_PCH and URA_PCH state. It is used also in CELL_DCH state Complete neighbouring cell lists can be provided to guarantee optimal cell re-selection and end-user QoS Allows the definition of 32 intra-frequency, 32 inter-frequency and 32 inter-system neighbouring cells for idle mode UEs All these neighbours were originally intended to be included in SIB11, but in the specifications the physical size of SIB11 data has capacity only for 47 cells In demanding environments, the existing size of SIB11 may not be enough because the intra-frequency neighbours are typically given the highest priority and as a result the interfrequency and inter-system neighbour cell lists may remain incomplete When relevant neighbours are missing from the SIB11, the UE cannot make optimal cell selection, which may lower the performance in call success rates SIB11bis is a backward compatible solution to correct the problem in SIB11 Pre-R6 UEs can not read SIB11bis, and their capability is indicated to the RAN The RNC may update the missing neighbours to legacy UEs in the Cell_DCH state.
63
64
parameter structure, defining SPI per TC, ARP and THP CrHandlingPolicy is not used anymore The Capacity Request Queue is ordered based on
SPI of the request Arrival time
65
SPI = Scheduling Priority Indicator 015 TC = Traffic Class (Conversational, Streaming, Interactive, Background) ARP = Allocation and Retention Priority from CN THP = Traffic Handling Priority from CN
66
67
68
Thank You !
69