Академический Документы
Профессиональный Документы
Культура Документы
Problem Summary:
In some occasions, the redirection back to LTE after a CS fallback procedure delays more than
expected.
Collected information:
• Planned tests were carried out with the collaboration of Telefónica. Traces were collected at the
same time the tests were executed.
• One user was making tests with his UE to reproduce the scenario under analysis.
• Emil traces were collected in eNB LPI_PUCARA.
• Traces were collected also in SGSN, MME and SAEGW.
• Also Traffica News events were checked for SGSN and MME.
EPC analysis:
• In Traffica News event check all the mobility events for 3G and 4G (RAU and TAU) were
successful.
• In the SGSN trace all the events are successful and no rejected or failed procedure in SGSN and
MME.
• In the FNG trace, all the requests are accepted for 3G and 4G and even it can be checked that
the UE is keeping the same IP address during all the tests.
In summary: from SGSN, MME and SAEGW side, all the registered mobility events are normal in
the CSFB procedure and all of them are successful. During the time the UE remained in 3G not
coming back immediatly to LTE, there are no request messages to packet core network.
• All the UE requests coming to eNB are processed and successfully completed in the eNB trace
collected during the tests.
• All the requests, both CSFB to go 3G layer and TAU requests to come back to LTE, are
completed successfully.
• There are no rejected procedures in LTE side.
• Considering these results, it’s needed to check 3G side in order to figure out the reasons of the
delay of return from 3G to 4G.
• It’s remarkable that, during the tests, in 3G side the UE continues camping in 3G and with
available services (voice or data). This means that RNC is not commanding the redirection to
LTE for any reason.
• State transition from Cell_DCH to Cell_FACH, • Channel type switch from HS-DSCH to DCH • CS RAB release trigger means case where an
Cell_PCH, URA_PCH due to inactivity. • Instead of waiting for resources in WCDMA, the UE has CS RAB and at least one active PS
• LTE Interworking allows to reselect when the UE UE is redirected to LTE layer RAB and then CS RAB is released (UE would
is in Idle, Cell_PCH and URA_PCH – now • This trigger is used only if UE has no CS RAB stay in CELL_DCH state in WCDMA).
layering to LTE is even quicker.
HS-
DSCH
Cell_DCH Cell_FACH
• The operator can decide which events triggers LTE Layering via setting appropriate value for SmartLTELayeringEnabled parameter:
• Enabled for state change (1),
• Enabled for state change and channel type switch (2),
• Enabled for state change and CS RAB release (3),
• Enabled for all triggers (4) TELEFONICA ECUADOR CONFIGURATION
11 © Nokia Solutions and Networks 2014
Redirection from 3G to LTE after CS fallback - Analysis of non fast return case
150
100
50
22/02/2016 1:00
22/02/2016 4:00
22/02/2016 7:00
22/02/2016 10:00
22/02/2016 13:00
22/02/2016 16:00
22/02/2016 19:00
22/02/2016 22:00
23/02/2016 1:00
23/02/2016 4:00
23/02/2016 7:00
23/02/2016 10:00
23/02/2016 13:00
23/02/2016 16:00
23/02/2016 19:00
Check of Smart LTE layering prevention in eNB LPI_PUCARA:
23/02/2016 22:00
24/02/2016 1:00
24/02/2016 4:00
24/02/2016 7:00
24/02/2016 10:00
24/02/2016 13:00
Redirection from 3G to LTE after CS fallback - Analysis of non fast return case
CONCLUSSIONS
• After analysis of the traces in EPC and LTE network collected during the tests, it can
be concluded that the system (LTE, EPC and 3G core networkg) is working as
expected and is not avoiding the return to LTE of the UE after a CS fallback
procedure.
• Analysis of 3G RAN configuration and counters collected by RNC rises up cases of
UEs not able to return to LTE because of a prevention timer.
• All these prevented UEs can enter in scenarios (mainly because of an HSPA call) that
avoid its return to LTE until the HSPA call is finished.