UE attach with LTE network as "Combined EPS/IMSI" then getting EPS only attach from network. EMM cause comes as "MSC temporarily not reachable". What will be the UE behaviour after getting this?
This behaviour defined in 24.301.
This is a temporary reject cause. So when this reject cause is received following is the behaviour:
1) Increment attempt counter by 1. Start T3411.
2) After expiry of T3411 attempt combined TA/LA update.
3) If successful, continue with normal operation.
3) Else if the same reject cause is received and attempt counter is less than 5, go back to step 1.
4) If attempt counter is greater than or equal to 5, then the next behaviour depends on the UE mode of operation and the status of IMS registration.
If IMS registration is successful, then stay on LTE irrespective of the UE mode of operation.
If IMS registration has failed/not supported:
a) If UE is in CS/PS mode 1(voice centric) of operation, disable LTE for operator determined duration and move to legacy (2G/3G), since voice is our priority. Generally the disable duration is the duration of T3402.
b) If it is in CS/PS Mode 2(data centric) of operation, then stay in LTE and attempt combined registration after expiry of T3402.
Wednesday, November 19, 2014
Sunday, June 1, 2014
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.
Saturday, October 26, 2013
Sunday, September 15, 2013
Subscribe to:
Posts (Atom)