Professional Documents
Culture Documents
Nemo Analysis Workshop
Nemo Analysis Workshop
1.Nemo Events and Definition 2.RRC and Layer3 messages 3.SIB Information,Measument Control (MC),Measurement Report (MR) 4.CS and PS Call Flow 5.Cell Reselection, SHO and ISHO
MOC
M T C
Block error ratio:BLER is measured from the CRC Transport Block (TB) is a basic unit that is exchanged between Layer 1 and Layer 2 (MAC). Layer 1 adds CRC for each TB and BLER is calculated from the CRC
Cell update causes in priority order: Uplink data transmission in URA_PCH, CELL_PACH Paging response in URA_PCH, CELL_PACH Radio link failure in CELL_DCH (*) Re-entering service area in CELL_FACH, CELL_PCH RLC unrecoverable error in all sub-states Cell reselection in CELL_FACH, CELL_PCH Periodical cell update in CELL_FACH, CELL_PCH
URA update causes in priority order: (the UE is in the URA_PCH sub-state) URA reselection Periodic URA update
RRC Modes
CELL_FACH
CELL_DCH
DCCH and if configured DTCH Dedicate physical channel in use UE location known on active set cell level UE responsible for measurement reporting Cell system information on BCCH RRC messages on DCCH
DCCH and if configured DTCH FACH used for higher layer data transfer, UE monitors FACH permanently Uplink transmission on RACH UE location known on serving cell level UE performs cell re-selection UE responsible for measurement reporting Cell system information on BCCH RRC messages on BCCH, CCCH and DCCH
What are the characteristics of the individual sub-states, when the UE is in the RRC connected mode? CELL_DCH In this sub-state, dedicated physical channels are allocated to the UE. DCCH and if configured DTCH information can be transmitted. There no need to identify the UE on a dedicated channel, because the physical channels are exclusively allocated to this UE. UTRAN knows the active set cells for the radio links and thus the location of the the UE. Also downlink shared channels can be allocated to the UE. In this state, the UE is capable to receive RRC messages on the DCCH (and BCCH, if it owns specific capabilities). The cell system information is broadcasted on the FACH. The UE reads the cell system information and acts accordingly. For instance, it determines the measurement quality and the reporting events from the cell system information. CELL_FACH This state was introduced for traffic situations, where only small amounts of data have to be transmitted. This is the case when only higher layer signalling information (NAS signalling) or small amount of user data (e.g. SMS messages) have to be transmitted. In this case, an exclusive allocation of one physical channel to the UE would result in a waste of resources. The UE is capable to receive and transmit DCCH and if configured DTCH information. Only common transport channel FACH can be used by the UE to transmit higher layer data, which it has to share with other UEs. Each UE must be explicitly addressed, for instance by the RNTI. It has to monitor the FACH permanently in the downlink, not to miss user data for it. The UEs FACH is mapped on one SCCPCH. In the uplink, it uses the shared transport channels for user data transfer, such as the RACH. The UE is only connected to one cell, and this is the location information, known within UTRAN. No soft handover takes place in this substate. The UE is responsible for cell re-selection. By listening to the cell system information from the BCCH, it gains all relevant measurement qualities, threshold values, neighbourhood lists to perform the cell re-selection process. Other relevant information is also learned from the BCCH. The UE receives RRC messages on the BCCH, CCCH and DCCH channels. Due to the discontinuous type of traffic, UTRAN can command the UE to perform periodic cell updates. CELL_PCH In this sub-state, the UEs current cell is known to the RNC. If the RNC wants to exchange data with the UE, it only needs to page the UE there. If the UE changes the cell, it must perform a cell update. Also periodical cell updates can be requested by UTRAN. To perform updates, the UE must change to the CELL_FACH sub-state. (Please note, that no uplink transmission is allowed in CELL_PCH/URA_PCH.) URA_PCH URA stands for UTRAN Registration Area. If the UE is in the CELL_PCH and moving fast, a lot of cell updates have to be performed. URAs are a combination of one or several cells under one C-RNC. URAs may overlap, i.e. a cell may belong to several URAs. If UTRAN wants to transmit something to the UE, it must page the UE within the URA. The UE is responsible for URA updates when it changes the URA and periodic URA updates when required by UTRAN.
System Information
Within UTRAN system information is broadcasted with the help of the RRC messages System Information, Paging Type I, and System Information Change Indication. Most system information parameters are determined by the RNC. The Node B is informed about the parameters via the NBAP message BCCH Information. Some system parameters can be made available by the Node B, such as interference values, which change fast. Given the system information, the UE is capable to decide, whether or how to access the PLMN via the existing cell. System information is organised in System Information Blocks (SIBs). System information is grouped into SIB 1 to SIB 18. Each SIB is responsible to carry a specific content. For instance, SIB 12 holds measurement control information and parameters. Depending on the UEs RRC state, it reads specific SIBs, and uses the transmitted parameters.
There is a huge amount of SIBs, which have to be read by the UE. This requires a lot of battery power.
Therefore, a Master Information Block (MIB) was introduced, which gives references and scheduling information about the SIBs. The MIB is transmitted in every 8th radio frame on the P-CCPCH (on position SFN mod 8 = 0, and with a TTI of 20 ms). For most of the SIBs used within the system, the MIB may carry a value tag. The only exceptions are SIB 15.2, SIB 15.3 and SIB 16. If a value tag is unchanged, the corresponding system information has not been modified. Thus, there is no need for the UE to read the SIB. SIB 7 has no value tag. It changes with each occurrence. Scheduling information is used to inform the UE, where and when a specific system information is transmitted.
System Information ( )
UTRAN
UE
RNC Node B
position on P-CCPCH: SFN mod 8 = 0 TTI: 20 ms value tag M: range 1..8
UTRAN can notify UEs, that a value tag in the MIB has been changed. Hereby, the information element BCCH Modification Info is broadcasted. There are two RRC messages, which can carry this information element: Paging Type 1 Some mobile phones have no radio link allocated, mobile phones, which are in the RRC idle mode, and in the RRC connected mode sub-states CELL_PCH and URA_PCH. This paging message is transmitted in all paging occasions in the cell. System Information Change Indication With this message, we address UEs in the CELL_FACH sub-state. Consequently, this message must be transmitted on every S-CCPCH, which carries FACHs. The System Information Change Indication message is transmitted on a BCCH, which must be mapped on FACHs in such a way, that every SCCPCH carries the BCCH Modification Change IE.
Within the IE BCCH Modification Change, even a BCCH Modification Time can be given, indicating to the UEs, when the value tags will change. Please note, that UEs in the CELL_DCH sub-state are addressed directly by the RNC via the Measurement Control message.
In this course documentation, we only describe the System Information Blocks (SIBs), which are used in Nokias RAN1, and SIB 4 and SIB16. Please note, that all SIBs are valid on cell level except for SIB 1, SIB 15.3, and SIB 16. SIB 1 and SIB 15.3 are valid on PLMN level, while SIB 16 is valid for equivalent PLMNs.
For each SIB, following characteristics were specified: Area scope: Where is the value tag valid: within one cell or within a PLMN/ equivalent PLMN? UE RRC state: When the SIB is valid? UE RRC state: When the SIB is read? Scheduling information: At which position is the SIB transmitted and what is its repetition period? Modification of system information: Is it indicated by a value tag, or is it timer based?
The UE receives all SIBs via the BCCH. There is only one exception: SIB 10. If a UE is capable to receive simultaneously one SCCPCH and one DPCH, than it receives SIB 10 on a FACH. Master Information Block (MIB): The MIB informs the UE about the supported PLMN types and the PLMN identity. The UE finds in the MIB also references to up to maxSIB (=32) SIBs, including their scheduling information and type. A MIB is valid in one cell. If a UE changes the cell, is must read the new cells MIB. The MIB is read in the RRC modes/states RRC idle, CELL_FACH, CELL_PCH and URA PCH. Its parameter are valid in the same states. A change of the MIB information is indicated by a value tag. In this course documentation, we only describe the System Information Blocks (SIBs), which are used in Nokias RAN1, and SIB 4 and SIB16. Please note, that all SIBs are valid on cell level except for SIB 1, SIB 15.3, and SIB 16. SIB 1 and SIB 15.3 are valid on PLMN level, while SIB 16 is valid for equivalent PLMNs.
SIB1
System Information Block 1 (SIB 1) This SIB is used to inform the UE about NAS system information. The NAS system information characterises the NAS domains. SIB 1 also delivers UE timers and counters, which have to be used by the UE in the RRC idle and RRC connected mode. For instance, a UE in the RRC connected mode uses the timer T305 for periodic cell and URA updates. SIB 1 is valid in one PLMN. The MIB is read in the RRC modes/states RRC idle, CELL_FACH, CELL_PCH and URA PCH. Its parameter are valid in the same states, and the the RRC sub-state CELL_DCH. If the UE selects a new cell, and the SIB 1 value tag has the same number as in the preceding cell, the same content is transmitted in this SIB. There is then no necessity for the UE to read this SIB after cell re-selection.
T302/N302 The CELL UPDATE/URA UPDATE retransmission timer (MS timer) T300/N300 The RRC CONNECTION REQUEST retransmission timer (MS timer) T312/N312 The timer for supervising successful establishment of a physical channel (MS timer) T309 The timer for supervising successful connection establishment in case of an inter-RAT cell re-selection (MS timer)
T316 This timer is started when the UE detects an out of service area in URA_PCH or CELL_PCH state. This timer is stopped when the UE detects an in service area. When the timer expires the UE initiates cell update procedure (MS timer).
T317 This timer is started when the T316 expires and the UE detects an out of service area. This timer is stopped when the UE detects an in service area. When the timer expires the UE transits to idle mode (MS timer)
SIB2
System Information Block 2 (SIB 2) This SIB contains an URA identity list. SIB 2 is read and valid in the RRC sub-state URA_PCH. A change of the SIB 2 information is indicated by a value tag.
SIB3
System Information Block 3 (SIB 3) This SIB contains relevant parameters for cell selection and re-selection. It also holds the cell identity and cell restriction data, such as cell barred IEs. SIB 3 must be read and is valid in the RRC idle mode. It is read and valid in the RRC connected mode sub-states CELL_FACH, CELL_PCH and URA_PCH, if SIB 4 is not broadcasted. A change of the SIB 3 information is indicated by a value tag.
SIB4
System Information Block 4 (SIB 4) This SIB holds mostly the same data fields as SIB 3, but it is read and valid only, when the UE is in the RRC connected mode. I.e, this optional SIB is read and valid in the CELL_FACH, CELL_PACH and URA_PCH substate. A change of the SIB 4 information is indicated by a value tag.
SIB5
System Information Block 5 (SIB 5) The parameters for the configuration of physical channels are broadcasted in this SIB. The parameters cover the PICH power offset, the AICH power offset, P-CCPCH, S-CCPCH and PRACH system information lists. SIB 5 must be read and is valid in the RRC idle mode. It is read and valid in the RRC connected mode sub-states CELL_FACH, CELL_PCH and URA_PCH, if SIB 6 is not available. A change of the SIB 5 information is indicated by a value tag.
SIB7
System Information Block 7 (SIB 7) This SIB holds fast changing parameters. Therefore no value tag is used for it. The UE has to read its parameters periodically. For that, an expiration timer (Expiration Time Factor) is broadcasted with this message. SIB 7 expires at max(32, 8 * Expiration Time Factor). Expiration Time Factor can have the values 2times, 4 times, 8 times ... 256 times. Its default value is 1. The fast changing parameters transmitted with SIB 7 include the UL interference and dynamic persistence level. It is read and valid in all states except for the CELL_DCH sub-state.
SIB11
System Information Block 11 (SIB 11) This SIB holds measurement control information. The UE gets here the relevant date for traffic measurement, intrafrequency measurements, etc. SIB 11 must be read and is valid in the RRC idle mode. It is read and valid in the RRC connected mode sub-states CELL_FACH, CELL_PCH and URA_PCH, if SIB 12 is not broadcasted. It is also valid in the RRC sub-state CELL_DCH, as long as the UE did not get a Measurement Control message from UTRAN and SIB 12 is not broadcasted. A change of the SIB 11 information is indicated by a value tag.
SIB11
SIB11
SIB12
System Information Block 12 (SIB 12) SIB 12 transmits measurement control information for UEs in the RRC connected mode. If not transmitted, the UEs take the parameters broadcasted with SIB 11. If available, SIB 12 is read and valid in the RRC connected mode sub-states CELL_FACH, CELL_PCH and URA_PCH. It is also valid in the RRC sub-state CELL_DCH, as long as the UE did not get a Measurement Control message from UTRAN. A change of the SIB 12 information is indicated by a value tag.
SIB16
System Information Block 16 (SIB 16) RB, TrCH, and PhyCH parameters are broadcasted, which are stored by the UE both in the RRC idle and RRC connected mode. The parameters are used during a handover to UTRAN. Consequently, these parameters stay valid, when the UE is connected to GSM and GPRS. This SIB is valid in all RRC states, and read in all RRC states except for the CELL_DCH. The UE reads and stores the parameters. A change of the SIB 16 information is indicated by a value tag.
DL SRB
UE in DUAL MODE
UE in 3G LOCKED MODE
UE
UTRAN
Node B RNC
System Information [BCCH] SIB 4 & SIB 12 (SIB 3 & SIB 11)
UE
UTRAN
Node B RNC
UTRAN
RNC
Node B SIB 3 [4]: parameters for cell selection and re-selection [in the RRC connected mode] SIB 11 [12] : measurement control information [in the RRC connected mode] read and valid: idle, CELL_FACH, CELL_PCH, URA_PCH. (SIB 11/12 is also valid in the CELL_DCH.)
Finally, UTRAN inform the UE, how to deliver the measurement reports: Delivery on an acknowledged or unacknowledged RLC, and Periodical or event triggered reporting.
In the RRC message Measurement Control, the is an PhyCH information elements, where the UE can gain DPCH compressed mode status information.
Measurement Control ( )
UE
RNC
setup/modify/release RLC AM/UM and periodical reporting/event triggered includes non-frequency related cell info
Intra-Frequency Measurements Inter-Frequency Measurements Inter-RAT Measurements UE-Internal Measurements Traffic Volume Measurements Quality Measurements UE Positioning Methods
Intra-frequency Measurements
Intra-frequency measurements are measurements on downlink physical channels at the same frequency as the active set. The measurement object is one cell. If the RRC message Measurement Control commands the UE to make intra-frequency measurement, it may contain among others: Intra-frequency cell info list (optional) Measurement quantity There are three different measurement quantities for the FDD mode: - Downlink Ec/N0 - Downlink received signal code power (RSCP) after despreading. - Downlink pathloss in dB = Primary CPICH Tx power - CPICH RSCP. Measurement validity The measurement validity describes, when the measurement has to be conducted. There are three options: - CELL_DCH state, - all states except the CELL_DCH state, and - all states. Reporting Criteria Reporting criteria outline, what kind of intra-frequency measurements have to be conducted. A set of intrafrequency measurements were specified, but it is the operators choice, which ones are used.
Cell 1
Cell 2
Cell 3
absolute threshold
time
Cell 1
Cell 2
Cell 3
Cell 4
Cell 5
Cell 6
Cell 7
Cell 8
Neighbour cells defined only for Cell 7 Cell 12
Cell 9
Cell 10
Cell 11
Cell 3
Cell11 Neighbour cells which are common to Cell 6 and Cell 7 Neighbour cells defined only for Cell 6 Cell 2 Cell7 Cell 10 Cell 4 Cell 8 Cell 12
Cell 5
Cell 6
Step 2
Cell 50
Cell 9 Cell 13 Cell 10 Cell 22 ... Cell 33 Common to 2 Neighbour Lists Cell2 Cell 7 Cell 9 Cell 11 Cell 15 Cell 10 Cell 37
Cell 4
Cell 41 Cell 6 .. ...
Cell 43
Step 3
Max 32 Cells
Step 1
Neighbour Cells Lists Neighbour Cells defined for only 1 Neighbour List: random selection
Cell 41
Cell 49
.. Cell 22 Three Cells in the Active Set
Step 4
NodeB
RRC: RRC Connection Request (RACH) NBAP: Radio Link Setup Request NBAP: Radio Link Setup Response ALCAP: ERQ (Establish Request) ALCAP: ECF (Establish Confirm) FP: Downlink Synch FP: Uplink Synch RRC: RRC Connection Setup (FACH) L1 Synchronization NBAP: Synchronization Indication RRC: RRC Connection Setup Complete (DCH) [RRCconnRepTimer1/2(100ms,1s)]
RNC
MGW/CN
RNC checks if resources are available: BTS, AC, Transmission. If not it sends RRC Connection Reject L1 Synchronization
RANAP: Direct Transfer (MM: Authentication Response) RANAP: Common ID RANAP: Security Mode Command RRC: Security Mode Command
UE
NodeB
RRC: Security Mode Complete
RNC
MGW/CN
RANAP: Security Mode Complete RRC: Uplink Direct Transfer (CC: Setup) RRC: Downlink Direct Transfer (CC: Call Confirmed) RANAP: Direct Transfer (CC: Setup)
RANAP: Direct Transfer (CC: Call Confirmed) RANAP: RAB Assignment Request
RAB Establishment
NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready ALCAP: ERQ (Establish Request) ALCAP: ECF (Establish Confirm) FP: Downlink Synch FP: Uplink Synch
RL modification procedure: SRB+DCH, HW resources checked Possible failure in AAL2 setup (Iub, Iur and Iu)
ALCAP: ERQ (Establish Request) ALCAP: ECF (Establish Confirm) NBAP: Radio Link Reconfiguration Commit) RRC: Radio Bearer Setup
Soft handover is not allowed during the RAB establishment procedure (The mobile can not add or remove cells in AS) this makes the UE and Node B particularly sensitive to mobility and dominance Timer wf_rb_setup_cpl (6s) is started when the RRC: Radio Bearer Setup message is sent to the UE In case the timer expires Iu Release Request is sent to the CN with release cause (radio_conn_lost)
RRC: Radio Bearer Setup Complete RANAP: RAB Assignment Response
UE
NodeB
RRC: Downlink Direct Transfer (CC: Alerting) RRC: Downlink Direct Transfer (CC: Connect) RRC: Uplink Direct Transfer (CC: Connect Acknowledge)
RNC
MGW/CN
RANAP: Direct Transfer (CC: Connect)
Call Established
RANAP: Location Report
RRC: Measurement Control
Call Disconnect
RRC: Uplink Direct Transfer (CC: Disconnect) RANAP: Direct Transfer (CC: Disconnect) RANAP: Direct Transfer (CC: Release) RRC: Downlink Direct Transfer (CC: Release) RANAP: Direct Transfer (CC: Release Complete) RANAP: Iu Release Command RANAP: Iu Release Complete RRC: Downlink Direct Transfer (CC: RRC Connection Release) RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete) RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete) RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete) NBAP: Radio Link Deletion Request NBAP: Radio Link Deletion Response ALCAP: ERQ (Establish Request) ALCAP: ECF (Establish Confirm)
RNC
RANAP: Paging
MGW/CN
L1 Synchronization
UE
NodeB
RRC: Security Mode Complete
RNC
MGW/CN
RANAP: Security Mode Complete RRC: Uplink Direct Transfer (CC: Setup) RRC: Downlink Direct Transfer (CC: Call Confirmed) RANAP: Direct Transfer (CC: Setup)
RANAP: Direct Transfer (CC: Call Confirmed) RANAP: RAB Assignment Request
RAB Establishment
NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready ALCAP: ERQ (Establish Request) ALCAP: ECF (Establish Confirm) FP: Downlink Synch FP: Uplink Synch
RL modification procedure: SRB+DCH, HW resources checked Possible failure in AAL2 setup (Iub, Iur and Iu)
ALCAP: ERQ (Establish Request) ALCAP: ECF (Establish Confirm) NBAP: Radio Link Reconfiguration Commit) RRC: Radio Bearer Setup
Soft handover is not allowed during the RAB establishment procedure (The mobile can not add or remove cells in AS) this makes the UE and Node B particularly sensitive to mobility and dominance Timer wf_rb_setup_cpl (6s) is started when the RRC: Radio Bearer Setup message is sent to the UE In case the timer expires Iu Release Request is sent to the CN with release cause (radio_conn_lost)
RRC: Radio Bearer Setup Complete RANAP: RAB Assignment Response
UE
NodeB
RRC: Downlink Direct Transfer (CC: Alerting)
RNC
MGW/CN
RANAP: Direct Transfer (CC: Alerting) RANAP: Direct Transfer (CC: Connect)
RRC: Downlink Direct Transfer (CC: Connect) RRC: Uplink Direct Transfer (CC: Connect Acknowledge) RANAP: Direct Transfer (CC: Connect Acknowledge)
Call Established
RANAP: Location Report
NodeB
NBAP: Radio Link Setup Request NBAP: Radio Link Setup Response AAL2SIG: ERQ AAL2SIG: ECF FP: Downlink Synch FP: Uplink Synch
RNC
SGSN
RNC checks if resources are available: BTS, AC, Transmission. If not it sends RRC Connection Reject L1 Synchronization
[RRCconnRepTimer1/2(100ms,1s)]
RNC
SGSN
RRC: Radio Bearer Setup RRC: Radio Bearer Setup Complete RRC: Measurement Control
RANAP: RAB Assignment Response RANAP: Direct Transfer (SM: Activate PDP Context Accept)
RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept) RRC: Measurement Repor (Trafic Volume Reports 4a) NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready AAL2SIG: ERQ AAL2SIG: ECF NBAP: Radio Link Reconfiguration Commit
RNC
SGSN
RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept) NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready AAL2SIG: ERQ AAL2SIG: ECF NBAP: Radio Link Reconfiguration Commit RRC: Uplink Direct Transfer (MM: Detach Request) RRC: Radio Bearer Release
RANAP: Direct Transfer (MM: Detach Accept) RRC: Downlink Direct Transfer (MM: Detach Accept) RANAP: Iu Release Command RANAP: Iu Release Complete RRC: Radio Bearer Release Complete RRC: RRC Connection Release RRC: RRC Connection Release Complete RRC: RRC Connection Release Complete RRC: RRC Connection Release Complete
RRC setup
Bearer setup
Soft Handover
Handover Types
Intra-Frequency Handovers
Softer Handover Handover between sectors of the same Node B (handled by BTS) No extra transmissions across Iub interface Maximum Ratio Combining (MRC) is occurring in both the UL and DL Soft Handover MS simultaneously connected to multiple cells (from different Node Bs) Extra transmission across Iub, more channel cards are needed (compared to non-SHO) Mobile Evaluated Handover (MEHO) DL/UE: MRC & UL/RNC: Frame selection combining Hard Handover Arises when inter-RNC SHO is not possible (Iur not supported or Iur congestion) Decision procedure is the same as SHO (MEHO and RNC controlled) Causes temporary disconnection of the (RT) user Can be intra-BS, intra-RNC, inter-RNC Network Evaluated Handover (NEHO) Decision algorithm located in RNC
Inter-Frequency Handover
Inter-RAT Handover
Handovers between GSM and WCDMA (NEHO)
121
2006 Nokia
Each neighbor cell is defined using the UTRAN cell identifier which comprises; MCC (Mobile Country Code) MNC (Mobile Network Code) RNC Identifier Cell Identifier = AdjsMCC = AdjsMNC = AdjsRNCid = AdjsCI
ADJS Parameters
The LAC (AdjsLAC) & RAC (AdjsRAC) are also in ADJS parameter set
The maximum number of neighbours that can be defined in RNC database is ADJS: 31 31 neighbours + serving cell = 32 cells to measure ADJI: 32/carrier, total 48 ADJG: 32 Total: max. 111 in RNC database Limitation due to specifications of SIB11/12 size
125
2006 Nokia
Soft Handover
HC supports the following measurement reporting events and features:
Event 1A: A primary CPICH enters the reporting range (Ncell addition) Event 1B: A primary CPICH leaves the reporting range (Ncell deletion) Event 1C: A non-active CPICH becomes better than an active primary CPICH (Ncell replacement) Cell individual offsets for modifying measurement reporting behaviour Mechanism for forbidding a neighbor ing cell to affect the reporting range
Handover decision performed by RNC based on measurements and available resources Admission Control can reject the branch addition in case the maximum load is achieved in DL (threshold + offset), valid both for RT and NRT bitrates. Hard blocking may prevent branch addition
127
2006 Nokia
AdditionWindo w 1 2
RNC
Ec/Io
DropWindow
3 time
DropTime
Measurement Report
133 2006 Nokia
135
2006 Nokia
Measurement Report
137 2006 Nokia
AS update? RNC
event e1c : { replacementActivationThreshold t3, reportingAmount ra-Infinity, reportingInterval ri0-5 }, hysteresis 4, timeToTrigger ttt100, reportingCellStatus withinActiveSet : e3 }
There are two mappings first is the signalled value to actual value mapping and second is the way in which hysteresis is applied in the event triggering equation (TS25.331) Once in connected mode the networks sends the same set of information elements via a measurement control message Nokias implementation is that the values in the measurement control message are the same as those within SIB 11 Events 6F and 6G are configured in a similar fashion i.e. within SIB 11 and subsequently with a measurement control message
138
2006 Nokia
P CPICH 1
Reportin g Range
P CPICH 2
AdjsEcNoOffset
Enlarging Cell 3 by x dB
P CPICH 3 time Reporting Event 1B
140 2006 Nokia
Reporting Event 1A
PCPICH3 is forbidden to affect the reporting range as its quality is quite unstable.
AdjsDERR
P CPICH 3
Time
141 2006 Nokia
Branch deletion
RRC: Measurement Report (e1b)
142
2006 Nokia
SHO Summary
Event Reporting cell status Triggering Condition Reporting Range/ Time to Trigger Hysteresis Addition Window/4 dB Addition Time /100 ms Reporting Interval Addition Reporting Interval /0.5 s -
Active set cells + Event 1A Monitored set 2 monitored set (Add) cells cells
Drop Window/ 6 dB
Replacement Window/2 dB
Replacement time/100 ms
3GPP reporting events 1A, 1B and 1C (also 6F and 6G) CPICH Ec/Io is used as a measurement quantity rather than CPICH RSCP
CPICH Ec/Io measurements are more accurate
1A and 1B reporting range is defined by strongest active set cell 1C reporting range is defined by weakest active set cell
143 2006 Nokia
This function is activated by EnableRRCRelease (HOPS parameter)/0=no (def),1 =yes The RRC connection is released if either:
AveEcNoDownlink + ReleaseMarginForAveEcNo(n) < AvEcNoNcell(n) EcNoDownlink + ReleaseMarginPeakEcNo(n) < EcNoNcell(n) ReleaseMarginForAveEcNo (HOPS) = average Eb/N0 margin [-6 6] dB, default 2.5dB ReleaseMarginPeakEcNo (HOPS) = peak Eb/N0 margin [-6 6] dB, default 3.5dB
144
2006 Nokia
Inter-RNC Mobility
Most of the times the UE hands over among WBTS belonging to the same RNC (Intra-RNC Handovers) However, what happens when the target WBTS is under a different WBTS?? 3GPP gives two different options to handle inter-RNC mobility in WCDMA
Anchoring: the UE will be connected to the CN via the old RNC. It is required Iur connection between the RNCs involved SRNS relocation: the UE will be connected to the CN via the new RNC. It is the Nokia implemented method
SRNS relocation *)
CN CN
Anchoring
CN CN
Iu
RNC
Iu Iur
RNC
Iu
RNC
Iu Iur
RNC
Iu
RNC
Iu Iur
RNC
Iu
RNC
Iu Iur
RNC
145
2006 Nokia
RelocationSupport =1
CN
Target RNC
UE
Start RelocPrep
RANAP:Relocation Request
Start RelocOverall
RANAP:Relocation Request Ack
Stop RelocPrep
RANAP:Relocation Command
Start RelocOverall
RNSAP:Relocation Commit
UP switching
Stop RelocOverall
RANAP:Iu Release
RANAP:Relocation complete
SRNC Relocation is initiated in the Serving RNC when all the cells of the active set belong to a different RNC. The SRNC sends a Relocation Required The CN evaluates if the relocation is possible and in that case, it sends a Relocation Request to the target RNC with parameters for the bearer establishment Relocation Command sent from CN to Source RNC with UTRAN information and bearer parameters After that, the Source RNC sends Relocation Commit message over Iur to the Target RNC When target RNC starts to act as Serving RNC, it sends a Relocation Detect message to CN. This message has no parameters At the same time UTRAN Mobility Information is sent to the UE, to inform that the relocation is performed After the confirm, the target RNC informs CN with Relocation Complete message that the relocation procedure was successful and Iu is released from source RNC
Stop RelocOverall
RANAP:Iu Release Complete
146
2006 Nokia
RelocationSupport =1
CN Target RNC
UE
Start RelocPrep
RANAP:Relocation Request
Start RelocOverall
RANAP:Relocation Request Ack
Stop RelocPrep
RANAP:Relocation Command
Start RelocOverall
Physical Channel Reconfiguration L1 sync. Established between BTS and UE RANAP:Relocation Detect
Because there is no Iur interface, combined SRNS relocation and HHO are done before the UE is completely under the target RNC The procedure is quite similar to the not UE involved case until Relocation Command The only difference in the Relocation Required message, the Relocation Type IE is set to "UE involved in relocation of SRNS"
Instead of Relocation Commit via Iur, the serving RNC sends a Physical CH Reconfiguration, after which the UE stops transmitting and receiving on the old radio links and starts on the new radio link
UP switching
Physical Ch Reconfig Complete RANAP:Relocation complete
Stop RelocOverall
RANAP:Iu Release
Stop RelocOverall
RANAP:Iu Release Complete
147
2006 Nokia
General
UL Quality deterioration
UE Tx power
CPICH RSCP
CPICH Ec/I0
Initiate Compressed Mode Configure GSM measurements UE Reports GSM RSSI measurements
PS
ISHO parameters
CPICH RSCP (Event 1F) Thresholds: HHoRscpThreshold HHoRscpCancel L3 filter: HHoRscpFilterCoefficient Timers: HHoRscpTimeHysteresis HHoRscpCancelTime DL DPCH power Threshold: GsmDLTxPwrThrXX Data rate threshold HHOMAxAllowedBitrateDL CPICH Ec/Io (Event 1F) Thresholds: HHoEcNoThreshold HHoEcNoCancel L3 filter: Done already for SHO Timers: HHoEcNoTimeHysteresis HHoEcNoCancelTime UL Quality Timer: ULQualDetRepThreshold Data rate threshold HHOMAxAllowedBitrateUL
UE Tx Power (Event 6A) Threshold: GsmUETxPwrThrXX L3 filter: GsmUETxPwrFilterCoeff Hysteresis margin: GsmUETxPwrTimeHyst Data rate threshold HHOMAxAllowedBitrateUL
Handover Triggering
(XX=AMR,CS,NrtPS,RtPS)
Decision Algorithm
AdjgTxPwrMaxTCH AdjgRxLevMinHO (n) GsmMeasAveWindow
Handover Execution
This seems to be too long time, because based on field measurements BSIC and RSSI delays are about 3 seconds, so it makes senses to reduce the value of this parameter to some value about 3 seconds, otherwise, if the BSIC or RSSI measurements fail or if the IS-HO execution is not possible to due low GSM RSSI levels, the network will not deactivate compressed mode until the timer of 10 seconds has expired. Thus, decreasing the parameter value will allow the UE/network to initiate a new IS-HO attempt. Proposed value for GSMMaxMeasPeriod is 6 GSMNcellSearchPeriod: 0
This is neighbor cell search period parameter, ISHO is not allowed until the are enough measurement reports given by this parameter O means that only 1 measurement result is enough for decision making Duration of the cell search period is calculated: GSMRepInterval * GSMNcellSearchPeriod).
151
2006 Nokia
Event Triggered Coverage/Capacity based HO fulfilled in RNC RNC commands selected UE(s) to start IF/IS measurements Measurements are done in Compressed Mode (CM) UE reports GSM cells with strongest RSSI signals to RNC RSSI measurements and BSIC verification for GSM cells RNC makes HO decision and commands UE to target cell
5 Coverage/Capacity HO Reasons (31 Intra-Freq neighbours) 48 Inter-Freq neighbours 32 Inter-System neighbours can be measured
Reporting cells are active set cells (max 3) + max 6 IFHO, max 6 ISHO neighb. Different decision methods for IF HO Only one decision method for IS HO
Node B
RNC
RRC: Measurement Control ISHO triggering (2 reasons are possible) Initial Compressed Mode Configuration
CN
GSM RSSI Measurem ent GSM BSIC Identification RANAP: Relocation Required
153
BSIC verification always performed for AMR calls no interrupt in voice call
2006 Nokia
Node B
RNC
RRC: Measurement Control ISHO triggering (5 reasons are possible)
CN
NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready NBAP: Radio Link Reconfiguration Commit RRC: Physical Channel Reconfiguration
RRC: Physical Channel Reconfiguration Complete NBAP: Compressed Mode Command RRC: Measurement Control RRC: Measurement Report RRC: Cell Change Order from UTRAN
154
In most cases BSIC verification is not required (data interrupt as UE moves to 2G) PS makes use of RRC: CELL CHANGE ORDER FROM UTRAN message
2006 Nokia
3. Low measured absolute CPICH Ec/No, event 1E/1F FMCI: IFHOcauseCPICHEcNo FMCG: GSMcauseCPICHEcNo
HO trigger
4. UE Tx power approaches its maximum allowed power, event 6A/6D FMCI: IFHOcauseTxPwrUL FMCG: GSMcauseTxPwrUL
5 . Low measured absolute CPICH RSCP, events 1E/1F FMCI: IFHOcauseCPICHrscp, FMCG: GSMcauseCPICHrscp
6 . Others (Not implemented in RAN 1.5): e.g. Traffic & load reason IS-HO, etc
Frequency Measuring Control for Inter-Frequency = FMCI Frequency Measuring Control for Inter-System (GSM) = FMCG
absolute threshold
1E: HHoEcNoCancelTime
1F: HHoEcNoTimeHysteresis
time
Cell 1
Cell 2
Cell 3
1E: HHoRscpCancel 1F: HHoRscpThreshold
absolute threshold
1E: HHoRscpCancelTime
Event 1F (A primary CPICH falls below an absolute threshold) parameters: Triggering conditions: Active set cells Hysteresis: not used in 1F Threshold used frequency: HHoRscpThreshold (FMCS)/ - 93 dBm Time-to-trigger: HHoRscpTimeHysteresis (FMCS)/ 100 ms Amount of reporting: infinity Reporting interval: not applied. Reporting cell status: max 3 active cells.
3G -> 2G Measurements
ISHO parameters
CPICH RSCP (Event 1F) Thresholds: HHoRscpThreshold HHoRscpCancel L3 filter: HHoRscpFilterCoefficient Timers: HHoRscpTimeHysteresis HHoRscpCancelTime DL DPCH power Threshold: GsmDLTxPwrThrXX Data rate threshold HHOMAxAllowedBitrateD L CPICH Ec/Io (Event 1F) Thresholds: HHoEcNoThreshold HHoEcNoCancel L3 filter: Done already for SHO Timers: HHoEcNoTimeHysteresis HHoEcNoCancelTime UL Quality Timer: ULQualDetRepThreshold Data rate threshold HHOMAxAllowedBitrateU L
UE Tx Power (Event 6A) Threshold: GsmUETxPwrThrXX L3 filter: GsmUETxPwrFilterCoeff Hysteresis margin: GsmUETxPwrTimeHyst Data rate threshold
HHOMAxAllowedBitrateUL (XX=AMR,CS,NrtPS,RtPS)
back prevention
GsmMinHoInterval
ISHO measurements
After HO triggering message is sent to RNC, a RRC message Measurement Control is sent to UE containing details of the measurement that the UE must execute. Measurement reporting is periodical. Max 6 GSM cells could be measured by UE and reported to RNC. No filtering in measurements by UE
RRC: Measurement control message (GSM RSSI measurements) UE
RNC
Upon reception of the measurements reported by the UE, RNC applies a sliding averaging window to the RXLEV measurements. The averaged levels are used as input to the IS-HO decision algorithm.
UE
RNC
The first measurement report has info from the best GSM cell: BCCH freq & RSSI, no filtering used in UE
IS-HO command
WCDM A
RRC: Measurement control message (BSIC decoding)
RSSI meas.
TRSSI depends on
Numbers of GSM cells in
BSIC verification
TBSIC depends on :
Transmission gap pattern for
RNC
the neighbour cell list Reporting interval Sliding averaging window Transmission gap pattern for RSSI measurements
BSIC decoding
Inter-RAT HO Decision
On this page, you find conditions, which have to be satisfied, before an inter-frequency handover can be conducted. The best neighbouring cell must fulfil following criterion (best according to Ec/No):
ISHO Decision
AVE_RXLEV_NCell(n) > AdjgRxLevMinHO(n) + max(0, AdjgTxPwrMaxTCH(n) - P_max)
GSM cell
AdjgRxLevMinHO(n)
-(48-32)/2 = -8 dB -8.5 EcNo < -8 -115 + 11 = -104 dBm -105 Rscp < -104
MW = 12 s
4
POOR GSM COVERAGE No suitable cell
ISUP signalling
ISUP signalling
2G signalling
UE shall stop measuring RSSI of RAT N and focus on best cells BSIC verificatio
Connected mode
2G -> 3G handover CS AMR 2G -> 3G handover PS 3G -> 2G handover CS AMR 3G -> 2G handover PS
3G -> 2G reselection
Cell Reselection Cell Selection S-Ccriteria The cell selection criteria S Squal = Q Qqualmin are defined as follows:
TS 25.304 5.2.3.1.2
qualmeas
The cell selection criterion S for a suitable cell is fulfilled when: Where:
Squal
Cell Selection quality value, (dB). Not applicable for TDD cells or GSM cells Srxlev Cell Selection RX level value (dB) Qqualmeas Measured cell quality value. The quality of the received signal expressed in CPICH Ec/N0 (dB) for FDD cells. Not applicable for TDD cells or GSM cells. Qrxlevmeas Measured cell RX level value. This is received signal, -115dBm CPICH RSCP for FDD cells (dBm), P-CCPCH RSCP -101dBm for TDD cells (dBm) and RXLEV for GSM cells (dBm). Qqualmin Minimum required quality level in the cell (dB). -18dB Not applicable for TDD cells or GSM cells. Qrxlevmin Minimum required RX level in the cell. (dBm) -115dBm Pcompensation max(UE_TXPWR_MAX_RACH P_MAX, 0) (dB) UE_TXPWR_ Maximum TX power level an UE may use when MAX_RACH accessing the cell on RACH (read in system information), (dBm) P_MAX Maximum RF output power of the UE, (dBm)
intra GSM
If Squal > Sintrasearch, UE need not perform intra-frequency measurements. If Squal <= Sintrasearch, perform intra-frequency measurements. If Squal > Sintersearch, UE need not perform inter-frequency measurements If Squal <= Sintersearch, perform inter-frequency measurements.
If Squal > SsearchRAT m, UE need not perform measurements on cells of RAT "m". If Squal <= SsearchRAT m, perform measurements on cells of RAT "m".
1
2 3 4
Sintrasearch =
S S intrasearch intersearch
Ssearch RAT
WCDMA CELL
Quality value. The quality value of the received signal expressed in CPICH_Ec/No or CPICH_RSCP_LEV for FDD cells as set by the Cell_selection_and_reselection_quality_measure information element, PCCPCH_RSCP_LEV for TDD cells and RXLEV for GSM cells. This specifies the hysteresis for serving cell that is of different radio access modes or technologies AND for serving FDD cell when cell_selection_and reselection-quality_measure is set CPICH RSCP.. This specifies the hysteresis for serving FDD cell when the cell_selection_and reselection-quality_measure is set CPICH Ec/No. This specifies the offset between the two cells when the neighbour cells that are of different radio access modes or technologies AND for neighbour FDD cells when cell_selection_and reselection-quality_measure is set CPICH RSCP This specifies the offset between the two cells when neighbour FDD cells when the cell_selection_and reselection-quality_measure is set CPICH Ec/No.
Concept
SintraSearch
First ranking of all the cells based on CPICH RSCP (WCDMA) and RSSI (GSM)
Rs = CPICH RSCP + Qhyst1 Rn= Rxlev(n) - Qoffset1
Serving WCDMA cell calculation, with hysteresis parameter Neighbour WCDMA or GSM cell calculation with offset parameter
Rn (GSM) > Rs (WCDMA) And Rxlev (GSM) >QrxlevMin Second ranking only for WCDMA cells based on CPICH Ec/No Rs = CPICH Ec/No + Qhyst2 Rn=CPICH_Ec/No(n)-Qoffset2
Yes
S-Criteria OK Fast MS
Cells with Lower HCS Priority than in Serving cell
Best R
Best R
Best R
Cell Reselection
Neighbour measurements summary SsearchRAT m
SlimitsearchRAT m
Sintersearch Sintrasearch
Sx=Squal= Ec/No
Intra-frequency Inter-frequency
Intrafrequency
Intra-frequency Inter-frequency
HCS used
Performance
There is no timer defined how long the GSM should be fulfilling the re-selection criteria However there is running average of 4 GSM measurements which provides some protection against ping pong (time vice based on DRX cycle length and as sliding window average) In case additional protection is needed it can be arranged by using the Qhyst1 parameter (for WCDMA serving cell RSCP) or AdjgQoffset1 (for GSM neighbouring cell RxLev) First ranking of all the cells based on CPICH RSCP (WCDMA) and RSSI (GSM) Rs = CPICH RSCP + Qhyst1 Rn= Rxlev(n) - Qoffset1
When to trigger the cell reselection to 2G depends greatly on: how much the 3G network is requested to be utilised target is to maximise the utilisation of WCDMA network but what is the desired CSSR at the same time maximise the quality minimise the possibility of ping pong Due to very different fading conditions, there should be couple of different parameter sets for 3G -> 2G reselection Outdoor, typical outdoor to dedicated indoor (in case of missing 3G indoor) 3G border Special indoor cases without dedicated 3G where the UE speed is high (e.g. tunnels)
2G -> 3G reselection
GSM MS starts WCDMA measurements if : RLA_C< F(Qsearch_I) for 0<Qsearch_I<=7 or RLA_C> F(Qsearch_I) for 7<Qsearch_I<=15
check
at least every 5 s
Measurement Updates: RLA_C value of the serving cell + least 6 strongest non serving GSM cells
If, for suitable UMTS cell & for a period of 5 s: CPICH RSCP > RLA_C + FDD_Qoffset and CPICH Ec/No FDD_Qmin
FDD_Qmin= -13 dB
FDD_REP_QUANT defines the reporting quantity for UTRAN cell (1=Ec/No or 0=RSCP, default 1) 3G_Search_PRIO parameter allows to extend the BSIC reporting interval from 10 s to 13s by checking the BSICs from non-serving BCCH carriers and also make WCDMA measurements as often as possible. Range is 0=no, 1=yes, default value 1 Defined in the SI2quater and PSI3quater if PBCCH is allocated.
old FDD_(GPRS) FDD_REP_ 3G_search_ Qoffset QUANT PRIO 2quater 2ter 2(3)quarter (PBCCH)
Parameter
Comment:
-
-28dB -24dB 24dB 28dB
Always select irrespective of RSCP value Reselect in case WCDAM RSCP > GSM RXLev (RLA_C) 28dB
FDD_Qmin >=-12
The rule to set the FDD_Qmin value has not been possible to be fulfilled until the specification change (05.08 v8.18.0, 2003-8) has been implemented to the UEs as below
QqualMin = -18dB
t
Camping in 3G Camping in 2G Camping in 3G
Fdd_Qmin mapping Aif parameter 0 1 2 3 4 5 6 7 Fdd_Qmin (old) [dB] -20 -19 -18 -17 -16 -15 -14 -13 Fdd_Qmin (new) [dB] -20 -6 -18 -8 -16 -10 -14 -12