Failure Event due to :
Showing posts with label WCDMA. Show all posts
Showing posts with label WCDMA. Show all posts
Thursday, April 10, 2014
Sunday, November 17, 2013
Power CAC Algorithm
~Algorithm 1 (ALGORITHM_FIRST): based
on UL/DL load measurement and load prediction (RTWP and TCP)
-admission decision based on predicted load increment upon admission of a new service-Based on the current cell load (indicated by the uplink load factor and downlink TCP) and the predicted load increment due to admission of the new service, the RNC determines whether the cell load will exceed the threshold upon admitting the new service. If yes, the RNC rejects the access request. If not, the RNC accepts the access request.
~Algorithm 2 (ALGORITHM_SECOND): based on Equivalent Number of User (ENU)
admission decision based on the ENU
-Depending on the current ENU and the access request, the RNC determines whether the ENU will exceed the threshold upon admitting a new service. If yes, the RNC rejects the request. If not, the RNC accepts the request.
~Algorithm 3 (ALGORITHM_THIRD): loose call admission control algorithm
-admission decision based on no load increment upon admission of a new service
-This algorithm assumes that load increment upon admission of a new service is 0. Based on the current cell load (indicated by the uplink load factor and downlink TCP), the RNC determines whether the cell load will exceed the threshold upon admitting the new service. If yes, the RNC rejects the access request. If not, the RNC accepts the access request.
-admission decision based on predicted load increment upon admission of a new service-Based on the current cell load (indicated by the uplink load factor and downlink TCP) and the predicted load increment due to admission of the new service, the RNC determines whether the cell load will exceed the threshold upon admitting the new service. If yes, the RNC rejects the access request. If not, the RNC accepts the access request.
~Algorithm 2 (ALGORITHM_SECOND): based on Equivalent Number of User (ENU)
admission decision based on the ENU
-Depending on the current ENU and the access request, the RNC determines whether the ENU will exceed the threshold upon admitting a new service. If yes, the RNC rejects the request. If not, the RNC accepts the request.
~Algorithm 3 (ALGORITHM_THIRD): loose call admission control algorithm
-admission decision based on no load increment upon admission of a new service
-This algorithm assumes that load increment upon admission of a new service is 0. Based on the current cell load (indicated by the uplink load factor and downlink TCP), the RNC determines whether the cell load will exceed the threshold upon admitting the new service. If yes, the RNC rejects the access request. If not, the RNC accepts the access request.
Friday, August 2, 2013
BLER and SIR
Block Error Rate (BLER) is an analysis of transmission errors on the radio interface.
It is based on analysis of cyclic redundancy check (CRC) results for radio link control (RLC) transport blocks and computed as below:
Signal-to-Interference Ratio (SIR), also known as the
carrier-to-interference ratio (C/I, CIR), is the quotient between the average
received modulated carrier power and the average received co-channel
interference power.
Example: Mobility movement > Handover trigger > SIR Error > UL BLER
Spreading Factor (SF) or Processing Gain
Spreading factor (SF) is the ratio of chip rate to bit rate
OR the ratio of the chips to baseband information rate. As after spreading, A
single bit of the user data is called chip.
Spreading factor is the concept of CDMA used in UMTS.
Spreading factors vary from 4 to 512 in FDD UMTS.
Spreading factor in dB indicates the processing gain as in a
spread spectrum system, the processing gain is the ratio of the spread (or RF)
bandwidth to the unspread (or baseband) bandwidth. It is the ratio of the
signal-to-noise ratio (SNR) of a processed signal to the SNR of the unprocessed
signal. The lower the spreading factor, the higher the data rate.

Wednesday, July 31, 2013
NAS Signaling Messages
The NAS signaling layer is used to exchange signaling messages between the UE and the CN.
1. Mobility Management:
LOCATION UPDATE, IMSI DETACH, AUTHENTICATION, TMSI REALLOCATION COMMAND, CM SERVICE, CM RE-ESTABLISHMENT
2. Call Control:
ALERTING, CALL CONFIRM, CALL PROCEEDING, CONNECT, CONNECT ACKNOWLEDGE, SETUP, RELEASE, STATUS
3. GPRS Mobility Management:
ATTACH, DETACH, ROUTING AREA UPDATE, SERVICE REQUEST, P-TMSI REALLOCATION, AUTHENTICATION AND CIPHERING
4. Session Management:
ACTIVATE PDP CONTEXT, DEACTIVATE PDP CONTEXT
1. Mobility Management:
LOCATION UPDATE, IMSI DETACH, AUTHENTICATION, TMSI REALLOCATION COMMAND, CM SERVICE, CM RE-ESTABLISHMENT
2. Call Control:
ALERTING, CALL CONFIRM, CALL PROCEEDING, CONNECT, CONNECT ACKNOWLEDGE, SETUP, RELEASE, STATUS
3. GPRS Mobility Management:
ATTACH, DETACH, ROUTING AREA UPDATE, SERVICE REQUEST, P-TMSI REALLOCATION, AUTHENTICATION AND CIPHERING
4. Session Management:
ACTIVATE PDP CONTEXT, DEACTIVATE PDP CONTEXT
Tuesday, July 30, 2013
Sunday, July 28, 2013
Saturday, July 27, 2013
SHO
Misunderstanding:
There are multiple RLs in both uplink and downlink during SHO.
In downlink, there are two/three RLs(radio links) during SHO. Please notice, radio link is just a logic concept which isn’t existed but just describes the connection between Node B and UE. But unlike downlink, there is only one RL in uplink. The reason is, in the downlink, scrambling code is used to distinguish the cells, whereas it’s used to identify UE in the uplink.
Therefore, Node B should send two/three copies of the same data via two/three different cells with different scrambling codes (2 way/3 way softer handover). At the same time, there is only one copy of data transmitting from UE to Node B. But all cells in active set will recieve it respectively and finally soft-combine it in RAKE.
The same mechanism is also applicable for E-DPDCH/E-DPCCH, as well as associated ul DPCCH and HS-DPCCH. As a result, all uplink channels have got diversity receiving gain.
ACK NACK DTX
ACK/NACK which is carried on uplink HS-DPCCH is sending from UE to inform Node B whether it has received/decoded certain transport block successfully.
The meanings of ACK/NACK/DTX are as obvious as their names express:
- ACK: Transport block is decoded correctly by UE;
- NACK: Transport block is decoded incorrectly;
- DTX: discontinuous transmission.
According to Chapter 6.2.6 ACK/NACK Transmit Power Reduction for HS-DPCCH in Mobile Communication Systems and Security by Man Young Rhee.
In Release 5, the UE always uses DTX in the ACK/NACK field of the HS-DPCCH except when an ACK or NACK is being transmitted in response to an HS-DSCH rtansmission. This means that if the UE fails to detect typical probability 0.01 of the HS-SCCH, the UE will use DTX in the corresponding ACK/NACK field. The Node B must avoid decoding this DTX as ACK if it is to avoid loss of the HS-DSCH TTI at the physical layer.
In summary:
- If HS-SCCH is not decoded successfully(no matter which part is wrong, part 1 or part 2), UE will not send any ACK/NACK info on HS-DPCCH, which is DTX.
- If HS-SCCH is successful but HS-PDSCH CRC is failed, NACK will be sent.
- Only if both HS-SCCH and HS-PDSCH are decoded correctly, UE will send ACK.
Subscribe to:
Posts (Atom)
