LTE Archives - Telecompedia https://telecompedia.net/category/lte/ Easy Explanation, Mostly Visualization Sun, 14 Mar 2021 13:14:36 +0000 en-US hourly 1 https://wordpress.org/?v=7.0.7 https://telecompedia.net/wp-content/uploads/2018/11/cropped-Original-2-32x32.png LTE Archives - Telecompedia https://telecompedia.net/category/lte/ 32 32 LTE UL Power Control in illustrations https://telecompedia.net/lte-ul-power-control-in-illustrations/ https://telecompedia.net/lte-ul-power-control-in-illustrations/#respond Fri, 05 Feb 2021 13:07:33 +0000 https://telecompedia.net/?p=1023 The UE will choose minimum power value from the calculation result to transmit user data on PUSCH. The formula consists of three sections: maximum allowed power of UE, open loop components and closed loop component. Here i means subframe, c presents serving cell. (1) Output power on PUSCH (2) Configured maximum allowed UE power (3) Number of resource blocks assigned for PUSCH (4) eNodeB expected power from the UE (5) Pathloss compensation factor (6) Downlink pathloss estimation by the UE (7) Parameter to adjust power based on MCS change (8) Here closed loop power control is used based on TPC commands by the serving cell to the UE. TPC means Transmit Power Control, used for adjustment of transmit power

The post LTE UL Power Control in illustrations appeared first on Telecompedia.

]]>
LTE UL Power Control in illustrations

The post LTE UL Power Control in illustrations appeared first on Telecompedia.

]]>
https://telecompedia.net/lte-ul-power-control-in-illustrations/feed/ 0
LTE Regular MIMO in illustrations https://telecompedia.net/lte-regular-mimo-in-illustrations/ https://telecompedia.net/lte-regular-mimo-in-illustrations/#respond Fri, 05 Feb 2021 12:54:48 +0000 https://telecompedia.net/?p=1019 LTE MIMO Transmission can work in two different schemes: SU-MIMO stands for Single User MIMO, MU-MIMO stands for Multi-User MIMO. In first scenario multiple data streams are transmitted to a single user terminal on a given time-frequency resource within a cell. For the second scenario, data streams are spatially multiplexed to multiple user terminals in the same time-frequency resource. In the 3GPP Release 12, up to eight data streams for SU-MIMO and up to four for MU-MIMO are supported. Key advantage of SU-MIMO is interference reduction, for MU-MIMO the advantage is multiplexing gain. In the illustration sample only DL direction was described (just to have an idea), similar is also applicable for UL with some limitation.

The post LTE Regular MIMO in illustrations appeared first on Telecompedia.

]]>
LTE Regular MIMO in illustrations

The post LTE Regular MIMO in illustrations appeared first on Telecompedia.

]]>
https://telecompedia.net/lte-regular-mimo-in-illustrations/feed/ 0
LTE DRX in illustrations https://telecompedia.net/lte-drx-in-illustrations/ https://telecompedia.net/lte-drx-in-illustrations/#respond Thu, 04 Feb 2021 12:06:13 +0000 https://telecompedia.net/?p=1001 DRX is used by user equipment to switch OFF and ON its transceiver (transmission & reception). It is called “Sleeping mode” when the UE switches OFF its transceiver, when it is ON then it is called “Active mode”.

The post LTE DRX in illustrations appeared first on Telecompedia.

]]>
LTE DRX in illustrations

The post LTE DRX in illustrations appeared first on Telecompedia.

]]>
https://telecompedia.net/lte-drx-in-illustrations/feed/ 0
LTE UL Power Control https://telecompedia.net/lte-ul-power-control/ https://telecompedia.net/lte-ul-power-control/#comments Mon, 05 Oct 2020 11:34:19 +0000 https://telecompedia.net/?p=718 The post LTE UL Power Control appeared first on Telecompedia.

]]>
Introduction

Power control is one of the most complicated subject in wireless communication technologies. Today we will try to have an overall idea about LTE Uplink Power Control with understanding each part of the calculation mechanism, but prior to diving to the topic let’s check a bit other things related to the power.

In physics, definition of power is the amount of energy transferred or converted per unit time. The unit of the power is Watt, but it can also be converted to other units such as dBm (Watt is a linear unit, while dBm is a logarithmic unit). Why we mentioned dBm here, because basically in radio telecommunication measurements the dBm or in longer version decibel-milliwatt is also used.

1 watt is equal to 30dBm (1W = 1000mW = 30dBm)
2 watts is equal to 33dBm (2W = 2000mW = 33dBm)
1 milliwatt is equal to 0 dBm (1mW = 0dBm)

Ok, but in the field when we open our drive test tool and we can see the measured signal level with negative values, e.g. -95dBm RSRP. Is it convertible to Watt too? Yes, we can with different magnitude: milliWatt(mW), microWatt(µW), nanoWatt(nW), picoWatt(pW), femtoWatt(fW), attoWatt(aW). Let see some examples for measured RSRP in Watt:

If two devices need to be communicated each other either over wire or wirelessly, then they need to transmit the required information with some amount of power. Let’s give an example from a mobile network. Imagine there are 100 mobile phone users under nearby same network cells and all the mobile phones are pushing their maximum power for transmission to the network cells in uplink direction. What will happen in this scenario? Intra-cell and inter-cell interference, huge handset power consumption. And consequently, it will cause for poor network performance and bad experience for customers.

Is there any way to eliminate the interference and avoid battery drain of the handsets? Yes, the answer is to control the transmission power of the mobile phones. Not to use the maximum power instead of that to use needed power if possible.

 

LTE Uplink Power Control

3GPP organization has technical specifications for power control in LTE. As we are talking about uplink direction here, then we need to mention PRACH, PUSCH, PUCCH and SRS power control. Each of them has own defined mathematical calculation formula. Vendors might have a bit different calculation including some extra features, but generally they should follow the specified standards. At first glance it might look as scary or boring, but don’t worry we will try to break into pieces and give simplified explanation for each part of the related formula.

 

Power Control on PRACH

Before initiation of physical random access procedure, the UE should receive the PRACH related information in advance from the higher layers through SIB2. You can find those information (parameters) in this page.

This is a short description from 3GPP: “From the physical layer perspective, the L1 random access procedure encompasses the transmission of random access preamble and random access response.  The remaining messages are scheduled for transmission by the higher layer on the shared data channel and are not considered part of the L1 random access procedure. A random-access channel occupies 6 resource blocks in a subframe or set of consecutive subframes reserved for random access preamble transmissions. The eNodeB is not prohibited from scheduling data in the resource blocks reserved for random access channel preamble transmission”

Now, let’s go one by one over each part of the PRACH Uplink Power control calculation formula:

  1. PPRACH is a preamble transmission power on physical random access channel (PRACH).
  2. PCMAX is configured maxium UE allowed output power. The transmitter characteristics are specified at the antenna connector of the UE with a single or multiple transmit antennas. For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed. Here an integral antenna means permanent fixed antenna, which may be built-in, designed as an indispensable part of the user equipment. On the following shortened table, we can find UE power class per frequency band.

  1. Preamble Received Target Power indicates target UE transmit power for the PRACH expected by the eNodeB. Lower value of this parameter will negative impact random access success rate, but higher value will improve it with causing interference on neighboring cells. Proper parameter definition is important (e.g. -104dBm, -106dBm etc.).
  2. PL is downlink path loss estimation calculated by the UE for the serving cell. This is the related formula:

 PLc = referenceSignalPower – higher layer filtered RSRP

where referenceSignalPower is delivered by the network to the UE through SIB2 (see details). Higher layer filtered RSRP means that the measured raw RSRP might not be reported to the network and Layer3 filtering can be applied to the measured result before using for evaluation of reporting criteria or for measurement reporting, by the following formula:

where

Mn is the latest received measurement result from the physical layer;

Fn is the updated filtered measurement result, that is used for evaluation of reporting criteria or for measurement reporting;

Fn-1 is the old filtered measurement result, where F0 is set to M1 when the first measurement result from the physical layer is received; and

a = 1/2(k/4), where k is the filterCoefficient for the corresponding measurement quantity received by the quantityConfig;

 

Power Control on PUSCH

Physical Uplink Shared Channel is used to transfer user data from the user equipment to the radio network. Like other physical channels when the data is transferred then it needs to be on a certain power for reaching to the destination. High transmit power can cause interference and fast UE battery drain, in opposite way with extreme low power may cause for undelivered data to the network. So, transmit power needs to be controlled.

But how the UE will be aware of the power control mechanism? The answer is serving cell itself. It will instruct the UE about the transmit power through PDCCH. The serving cell sends scheduling information to the UE over PDCCH, then the UE starts to transmit user data on PUSCH. The UE already knows which subframe, MCS and how many resource blocks will be used with the instruction. Now the further step is to calculate transmit power on PUSCH for each subframe (so calculation is based on every 1ms) with using below formula:

  1. PPUSCH is transmit power of UE on physical uplink shared channel (PUSCH).
  2. PCMAX is configured maxium UE allowed output power. For details see above in Power Control on PRACH. Same description is valid for PUSCH too.
  3. MPUSCH is the bandwidth of the PUSCH resource assignment expressed in number of resource blocks.
  4. P0_PUSCH is a composition of cell specific and UE specific components configured by higher layers and delivered to the UE to be used in power calculation to transmit on PUSCH, it is also described like eNodeB expected power or eNodeB target received power in some vendor libraries:

P0_PUSCH =P0_NOMINAL_PUSCH + P0_UE_PUSCH

  1. α (pronunciation is Alpha [ˈælfə]) is used as pathloss compensation factor. It is provided by the serving cell to the UE to be used for PUSCH power calculation in open loop. Following values can be setup {0, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1}.
  2. PL is downlink path loss estimation calculated by the UE for the serving cell. For details see above in Power Control on PRACH. Same description is valid for PUSCH too.
  3. ΔTF,c (i) depends on deltaMCS-Enabled parameter whether a UE needs to adjust the transmit power based on the MCS changes or not. It also has own small formula, let’s have a look:

where,

  • BPRE is number of information bits per resource element for the scheduled MCS.
  • Ks depends on deltaMCS-Enabled parameter switch. If it enabled then Ks is 0, if the switch is disabled then Ks is 1.25. The parameter indication is provided by the serving cell to the UE through RRC Connection Setup message.

Amazing! We have come a long way. It doesn’t look so easy, but we are trying to simplify for you. Let’s take a breath and go to the last piece of the formula which is closed loop part. So far the formula was presenting open loop power control section.

  1. fc (i ) is closed loop power control component and the current PUSCH power control adjustment state for serving cell which is defined by following formulas (a means cumulative, and b means absolute based on Accumulation-enabled parameter provided by higher layers):

δPUSCH  referred to as a TPC command and is signaled on PDCCH with DCI Format0 or DCI Format3/3A on subframe i – KPUSCH for serving cell. For FDD, KPUSCH is 4 subframes (4ms). For TDD, it depends on UL/DL configuration as below:

Above we mentioned TPC command, what does it mean? TPC or with a complete name Transmit Power Control is used in Closed Loop Power Control mechanism to instruct the user equipment to adjust its transmit power (increase or decrease).

 

Power Control on PUCCH

Physical Uplink Control Channel (PUCCH) is used to carry uplink control information from the UE to the radio network. The conveyed message might be formatted per information type, number of bits. And this type of formations is called PUCCH Formats. Here are some examples such as PUCCH Format1, PUCCH Format1a, PUCCH Format2 and others. The carried information range is large, here we can see just few of them: scheduling request, acknowledgement responses or retransmission requests, channel quality index.

As other physical uplink channels, there should also be some specified standards on PUCCH to control transmission power. Here are we have it:

  1. PPUCCH is transmit power of UE on physical uplink control channel (PUCCH).
  2. PCMAX is configured maxium UE allowed output power. For details see above in Power Control on PRACH. Same description is valid for PUCCH too.
  3. P0_PUCCH is a composition of cell specific and UE specific components configured by higher layers and delivered to the UE to be used in power calculation to transmit on PUCCH.
  4. PL is downlink path loss estimation calculated by the UE for the serving cell. For details see above in Power Control on PRACH. Same description is valid for PUCCH too.
  5. h(nCQI, nHARQ) is a PUCCH format dependent value, in different PUCCH Format the result might be different.
  • nCQI: corresponds to the number of information bits for the channel quality information
  • nHARQ: is the number of HARQ-ACK bits sent in subframe
  1. ΔF_PUCCH(F ) each value of this parameter corresponds to a PUCCH Format and impacts on PUCCH transmit power. It is delta value and the unit is dB. For instance, ΔF_PUCCH for PUCCH Format1 might be set as -2dB, 0dB or 2dB.
  2. ΔTxD(F’): if the UE is configured by higher layers to transmit PUCCH on two antenna ports, the value of this parameter is provided by higher layers for each PUCCH format; otherwise the value is 0.
  3. g(i) is closed loop power control component and the current PUCCH power control adjustment state. It also has small formula, let’s skim on it:

  • For FDD, M=1 and k0 = 4
  • For TDD, values of M and km depends on UL/DL configuration.
  • δPUCCH referred to as a TPC command and is signaled on PDCCH with DCI format 1A/1B/1D/1/2A/2/2B/2C/2D

 

Power Control on SRS

Sounding Reference Signal (SRS) is a kind of transmitted signal from UE to the serving cell on the last symbol of the subframe of SC-FDMA. If the entire uplink bandwidth could be used all the time, then we would not need such kind of reference signal. But it cannot be, so we would need to use it. Then what is the purpose of this this? The purpose is to help the eNodeB to estimate channel quality of uplink path at different frequencies.

If we are talking about transmission between the UE and eNodeB then it means, there is a power usage and we need to control it not make side effects.

  1. PSRS is transmit power of UE on sounding reference signal (SRS).
  2. PCMAX is configured maxium UE allowed output power. For details see above in Power Control on PRACH. Same description is valid for SRS too.
  3. PSRS_OFFSET(m), basically SRS follows similar PUSCH power control calculation method. PSRS_OFFSET indicates the power offset of the sounding reference signal to the PUSCH. The unit is dB, and configurable (e.g. -4.5,-3,-1.5,0,1.5,3 depends on vendor).
  4. MSRS is the bandwidth of the SRS transmission expressed in number of resource blocks
  5. Following three parameters are same with PUSCH power control parameters, you can find details above in PUSCH clause: P0_PUSCH ,α, PL and fc (i )
 
References: 3GPP 36.101, 3GPP 36.213, 3GPP36.331

The post LTE UL Power Control appeared first on Telecompedia.

]]>
https://telecompedia.net/lte-ul-power-control/feed/ 1
LTE DRX (Discontinuous Reception) https://telecompedia.net/lte-drx-discontinuous-reception/ https://telecompedia.net/lte-drx-discontinuous-reception/#respond Mon, 05 Oct 2020 01:16:36 +0000 https://telecompedia.net/?p=685 The post LTE DRX (Discontinuous Reception) appeared first on Telecompedia.

]]>
  The feature which we will talk about is not new and proposed in initial release of LTE 3GPP standards, but it was not common to be fully used by all mobile operators until some years ago.

  Here we will try to give general idea for DRX feature in Idle Mode and Connected Mode. 

  Once new type of mobile terminals with wide screen arrived to the market, or another case many mobile applications started to be used by the subscribers then fast battery drain become bothering.

  Of course, there was a most effective solution for this issue, and it was DRX or in other word Discontinuous Reception. Similar features exist in legacy technologies too, but in this article the topic is only LTE DRX.

  Some of the mobile operators could achieve 40%-45% power saving with DRX in their trials, sometimes less or even no effectiveness was observed in some terminals (it might be related with chipset producer). But generally, DRX is a powerful option for energy saving.

  When a new feature was invented, definitely we can see its advantages and also disadvantages. We already know about its positive part which is energy saving at mobile equipment, but what about side effect?

  Side effect or negative part or whatever we want to call are packet delay and packet loss (e.g. eNodeB can schedule data at specified time but the UE may be in sleeping mode at that time). Parameters of DRX are very sensitive, if any unreasonable value are defined on it then it can cause for serious QoS degradation.

  Typically a UE (user equipment) should always listen to the network to see if there is a new data for downlink or need to wait for UL Grant to transfer the data. This notification arrives through PDCCH channel. The PDCCH mapped to the first OFDM symbols in every downlink subframe, it can be 1, 2, and 3 symbols too (depends on configuration).

Let’s come back to DRX

  • Question 1: What is the relation between UE monitoring the PDDCH on each subframe and DRX ?
  • Answer 1: The relation is power consumption, where the UE spends huge energy if it continuously keeps monitoring and decodes each PDCCH message.
  • Question 2: How does the DRX help to save energy at UE side ?
  • Answer 2: DRX will let the UE not to listen every PDCCH. The UE will monitor the PDCCH in a specified period and then it will switch OFF its transceiver.

On the following images we can see generic illustrations of DRX Disabled and DRX Enabled scenarios.

  • On DRX disabled option, the UE keeps monitoring the PDCCHs on each subframe.
  • On DRX enabled option, the UE monitors the PDCCH on a predefined time durations then goes to sleep.

This is not an actual DRX working procedure, it is just for giving an idea how the DRX is influencing the UE power consumption. DRX can work in RRC Connected and RRC Idle modes, it is also called C-DRX and Idle Mode DRX respectively.

  • C-DRX has two stages as Short DRX Cycle and Long DRX Cycle. The Short DRX Cycle is optional, it is mostly used to avoid immediate action for large sleeping mode of Long DRX Cycle. It is clear from the below illustrations or in this version (see All in One).
  • The PDCCH monitoring in Idle Mode DRX happens on Paging Occasion per Paging DRX cycle

  Now let’s have a look one complete DRX procedure including all steps. The parameter values are not from actual network configurations, so it should not be considered as reference. The purpose is to draw an exemplification of DRX.

From left to right:

  • Each rectangle is a subframe, duration is 1ms
  • Data Info: there is scheduled new data for the UE, obtained the information from PDCCH
  • On green parts there are data transmission or reception
  • DRX Inactivity Timer: Specifies the number of consecutive PDCCH-subframe(s) after successfully decoding a PDCCH indicating a new UL or DL user data transmission for this UE.
  • DRX Short Cycle Timer: This parameter specifies the number of consecutive subframe(s) the UE shall follow the short DRX cycle after the DRX Inactivity Timer has expired.
  • On Duration Timer: Specifies the number of consecutive PDCCH-subframe(s) at the beginning of a DRX Cycle where UE transceiver is ON to listen the PDCCH.

 

  • C-DRX parameters are delivered to UE through RRC ConnectionReconfiguration or RRC Connection Setup. Once no any new data was decoded while listening period (onDurationTimer) and the times passed through Short DRX Cycles and Long DRX Cycles the time reaches to be releasing of RRC Connection with RRC Connection Timer expiration. This release command comes from the network. When the RRC Connection release command comes then the UE moves to Idle Mode, next hop is DRX Mode in Idle Mode where the UE wakes up on each Paging DRX Cycles and keeps its ear on PDCCH to see if there is any new data for the UE (e.g. Downlink) through paging messages.
  • Idle Mode DRX parameters are broadcasted with SIB2. The frames that paging messages are transmitted over the Uu interface are fixed. These fixed positions are indicated by the paging frames (PFs) and the paging occasion (PO) subframes. One PF is one radio frame, which may contain one or multiple POs. One PO is a subframe containing the paging radio network temporary identifier (P-RNTI), which is transmitted over the PDCCH. The UE reads paging messages over the physical downlink shared channel (PDSCH) according to the P-RNTI.

 

   Let’s describe the process one more time. The UE made call setup then requested UL Grant to send data or received DL Grant for downlink data. We can see on green part. After some time, there is no any new scheduled data for the UE and DRX Inactivity Timer started. When the DRX Inactivity Timer expires as a second step Short DRX Cycles starts to run (it is optional, some operator do not use), if no any data arrives or requested during that period then next step is Long DRX Cycles. If the UE keeps its passive status (no UL/DL data) then RRC Connection will be released by the serving cell once the RRC Inactivity Timer expires. After release of RRC Connection the UE moves to Idle Mode and starts to use Idle Mode DRX for monitoring PDCCH.

The post LTE DRX (Discontinuous Reception) appeared first on Telecompedia.

]]>
https://telecompedia.net/lte-drx-discontinuous-reception/feed/ 0
LTE Regular DL MIMO https://telecompedia.net/lte-regular-dl-mimo/ https://telecompedia.net/lte-regular-dl-mimo/#respond Sun, 04 Oct 2020 23:36:57 +0000 https://telecompedia.net/?p=664 The post LTE Regular DL MIMO appeared first on Telecompedia.

]]>
Introduction

Radio side of the network is more complicated in comparison with other domains, because of mobility and user behaviour. A user can be nearby the serving cell under perfect radio environment, and another user can be in the cell edge with very bad radio coverage. So consequently, one of them may be able to get very good experience but other not. It is just one of the simple examples. Both users are very important for the operators and need to deliver better service to them. But how?

In that reason radio equipment manufacturers always spend a huge of amount for their research and development departments to invent or enhance the existing features to overcome such problems.

One of the crucial features in LTE is MIMO which we will talk about, it is used to for radio link robustness, improve spectral efficiency and enhance user data throughput. As we can see here MIMO has several options, not just to robust radio link and it can also give another benefit.

MIMO is a complex technique in terms of working principle and is already used for legacy technologies: e.g WiFi, HSPA+, WiMax, LTE and LTE-Advanced.

Multiple-input and Multiple-output is the complete name of MIMO, below quote is from Wikipedia:

“At one time, in wireless the term “MIMO” referred to the use of multiple antennas at the transmitter and the receiver. In modern usage, “MIMO” specifically refers to a practical technique for sending and receiving more than one data signal simultaneously over the same radio channel by exploiting multipath propagation.”

What we can understand from the quote, in modern usage the MIMO is mostly used for different signal streams to be transmitted simultaneously with taking advantage of multipath propagation and it will result higher data throughput.

 

MIMO Overview

In MIMO terminology we can see multiple antenna configurations:

SISO

Single Input Single Output, it is very simple configuration in antenna system. Only one transmit and one receive antenna is used. No diversity, no extra option to improve SINR and data throughput. Due to multipath signal effect, this system is vulnerable.

SIMO

Single Input Multiple Output, it is also known as Receive Diversity. The receiver will receive same data by multiple receiver points and will make selection of best signal (Switched Diversity) or combining (Maximum Ratio Combining – MRC) to improve signal to noise ratio. Because of the different transmission paths, the receiver sees two differently faded signals.

MISO

Multiple Input Single Output, also known as Transmit Diversity: same versions of the data will be transmitted over different path to improve link reliability. It is like redundant versions on different path.

MIMO

Multiple Input Multiple Output,

  • More than one antenna in both receiver and transmitter sides
  • Mostly intended for two types of benefits:
  • Spatial Multiplexing: an information which is going to be transmitted will be separated into multiple streams and transmitted independently through different paths. Target is to improve data throughput at receiver side, but not helps for radio link reliability.
  • Diversity Gain: each channel towards to the receiver may experience different level of fading and interference. Here on different channels, multiple versions of the same information are transmitted and selection or combining happens on receivers’ side. From such kind of multipath propagation, the diversity technique may exploit a gain which is called Diversity Gain. Tradeoff is obvious between Spatial Multiplexing and Diversity Gain.

Transmission Modes

3GPP specified variety versions of antenna techniques for different usage scenarios and classified them under Transmission Mode numbers for DL and UL separately. Classification might be due to capacity, link reliability, high speed user or low speed user, beamforming etc.

 

The post LTE Regular DL MIMO appeared first on Telecompedia.

]]>
https://telecompedia.net/lte-regular-dl-mimo/feed/ 0
EPS Session Management Timers – UE side https://telecompedia.net/eps-session-management-timers-ue-side/ https://telecompedia.net/eps-session-management-timers-ue-side/#respond Wed, 15 Jul 2020 07:00:45 +0000 http://telecompedia.net/?p=527 EPS session management timers – UE side   TIMER NUM. TIMER VALUE STATE CAUSE OF START NORMAL STOP ON THE 1st, 2nd, 3rd, 4th EXPIRY (NOTE 1) T3480 NOTE 2 NOTE 3 8s In WB-S1/CE mode, 16s PROCEDURE TRANSACTION PENDING BEARER RESOURCE ALLOCATION READ MORE

The post EPS Session Management Timers – UE side appeared first on Telecompedia.

]]>
EPS session management timers at UE side: T3480, T3481, T3482, T3492, T3493, Back-off timer

EPS session management timers – UE side

 

TIMER NUM.

TIMER VALUE

STATE

CAUSE OF START

NORMAL STOP

ON THE
1st, 2nd, 3rd, 4th EXPIRY (NOTE 1)

T3480
NOTE 2
NOTE 3

8s

In WB-S1/CE mode, 16s

PROCEDURE TRANSACTION PENDING

BEARER RESOURCE ALLOCATION REQUEST sent

 

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST received or MODIFY EPS BEARER CONTEXT REQUEST received or BEARER RESOURCE ALLOCATION REJECT received

Retransmission of BEARER RESOURCE ALLOCATION REQUEST

 

 

T3481
NOTE 2
NOTE 3

8s

In WB-S1/CE mode, 16s

PROCEDURE TRANSACTION PENDING

BEARER RESOURCE MODIFICATION REQUEST sent

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST received or MODIFY EPS BEARER CONTEXT REQUEST received or DEACTIVATE EPS BEARER CONTEXT REQUEST received or BEARER RESOURCE MODIFICATION REJECT received

Retransmission of BEARER RESOURCE MODIFICATION REQUEST

T3482
NOTE 2
NOTE 3

8s

In WB-S1/CE mode, 16s

PROCEDURE TRANSACTION PENDING

An additional PDN connection is requested by the UE which is not combined in attach procedure

ACTIVE DEFAULT EPS BEARER CONTEXT REQUEST received or PDN CONNECTIVITY REJECT received

Retransmission of PDN CONNECTIVITY REQUEST

T3492
NOTE 2
NOTE 3

6s

In WB-S1/CE mode, 14s

PROCEDURE TRANSACTION PENDING

PDN DISCONNECT REQUEST sent

DEACTIVATE EPS BEARER CONTEXT REQUEST received or PDN DISCONNECT REJECT received

Retransmission of PDN DISCONNECT REQUEST

T3493
NOTE 2

4s

In WB-S1/CE mode, 12s

PROCEDURE TRANSACTION PENDING

REMOTE UE REPORT sent

REMOTE UE REPORT RESPONSE received

Retransmission of REMOTE UE REPORT

Back-off timer

 

 

defined in 3GPP TS 24.008 [13]

 

 

NOTE 1: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description.

NOTE 2: In NB-S1 mode, then the timer value shall be calculated as described in subclause 4.7.

NOTE 3: In WB-S1 mode, if the UE supports CE mode B and operates in either CE mode A or CE mode B, then the timer value is as described in this table for the case of WB-S1/CE mode (see subclause 4.8).

 

NOTE 1: The back-off timer is used to describe a logical model of the required UE behaviour. This model does not imply any specific implementation, e.g. as a timer or timestamp.

NOTE 2: Reference to back-off timer in this section can either refer to use of timer T3396 or to use of a different packet system specific timer within the UE. Whether the UE uses T3396 as a back-off timer or it uses different packet system specific timers as back-off timers is left up to UE implementation.

The post EPS Session Management Timers – UE side appeared first on Telecompedia.

]]>
https://telecompedia.net/eps-session-management-timers-ue-side/feed/ 0
EPS Session Management Timers – Network side https://telecompedia.net/eps-session-management-timers-network-side/ https://telecompedia.net/eps-session-management-timers-network-side/#respond Wed, 15 Jul 2020 06:56:52 +0000 http://telecompedia.net/?p=523 EPS session management timers – network side TIMER NUM. TIMER VALUE STATE CAUSE OF START NORMAL STOP ON THE 1st, 2nd, 3rd, 4th EXPIRY (NOTE 1) T3485 NOTE 2 NOTE 3 8s In WB-S1/CE mode, 16s BEARER CONTEXT ACTIVE PENDING ACTIVATE DEFAULT EPS READ MORE

The post EPS Session Management Timers – Network side appeared first on Telecompedia.

]]>
LTE EPS session management timers at network side: T3485, T3486, T3489, T3495

EPS session management timers – network side

TIMER NUM.

TIMER VALUE

STATE

CAUSE OF START

NORMAL STOP

ON THE
1st, 2nd, 3rd, 4th EXPIRY (NOTE 1)

T3485
NOTE 2
NOTE 3

8s

In WB-S1/CE mode, 16s

BEARER CONTEXT ACTIVE PENDING

ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST sent

 

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST sent

ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT received

or ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT received

or ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT received

or ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT received

Retransmission of the same message

T3486
NOTE 2
NOTE 3

8s

In WB-S1/CE mode, 16s

BEARER CONTEXT MODIFY PENDING

MODIFY EPS BEARER CONTEXT REQUEST sent

MODIFY EPS BEARER CONTEXT ACCEPT received

or MODIFY EPS BEARER CONTEXT REJECT received

Retransmission of MODIFY EPS BEARER CONTEXT REQUEST

T3489
NOTE 2
NOTE 3

4s

In WB-S1/CE mode, 12s

PROCEDURE TRANSACTION PENDING

ESM INFORMATION REQUEST sent

ESM INFORMATION RESPONSE received

 

Retransmission of ESM INFORMATION REQUEST on 1st and 2nd expiry only

T3495
NOTE 2
NOTE 3

8s

In WB-S1/CE mode, 16s

BEARER CONTEXT INACTIVE PENDING

DEACTIVATE EPS BEARER CONTEXT REQUEST sent

DEACTIVATE EPS BEARER CONTEXT ACCEPT received

Retransmission of DEACTIVATE EPS BEARER CONTEXT REQUEST

NOTE 1: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description.

NOTE 2: In NB-S1 mode, then the timer value shall be calculated as described in subclause 4.7.

NOTE 3: In WB-S1 mode, if the UE supports CE mode B and operates in either CE mode A or CE mode B, then the timer value is as described in this table for the case of WB-S1/CE mode (see subclause 4.8).

 

The post EPS Session Management Timers – Network side appeared first on Telecompedia.

]]>
https://telecompedia.net/eps-session-management-timers-network-side/feed/ 0
EPS Mobility Management Timers – UE side https://telecompedia.net/eps-mobility-management-timers-ue-side/ https://telecompedia.net/eps-mobility-management-timers-ue-side/#respond Wed, 15 Jul 2020 06:50:29 +0000 http://telecompedia.net/?p=520 EPS mobility management timers – UE side TIMER NUM. TIMER VALUE STATE CAUSE OF START NORMAL STOP ON EXPIRY T3402 Default 12 min. NOTE 1 EMM-DEREGISTERED EMM-REGISTERED At attach failure and the attempt counter is equal to 5. At tracking area READ MORE

The post EPS Mobility Management Timers – UE side appeared first on Telecompedia.

]]>
LTE EPS mobility management timers at UE side: T3402, T3410, T3411, T3412, T3416, T3417, T3418, T3420, T3421, T3423, T3430, T3440, T3442, T3444, T3445

EPS mobility management timers – UE side

TIMER NUM.

TIMER VALUE

STATE

CAUSE OF START

NORMAL STOP

ON
EXPIRY

T3402

Default 12 min.

NOTE 1

EMM-DEREGISTERED

EMM-REGISTERED

At attach failure and the attempt counter is equal to 5.

At tracking area updating failure and the attempt counter is equal to 5.

ATTACH ACCEPT with EMM cause #16 or #17 and the attempt counter is equal to 5 for CS/PS mode 2 UE, or ATTACH ACCEPT with EMM cause #22, as described in subclause 5.5.1.3.4.3.

TRACKING AREA UPDATE ACCEPT with EMM cause #16 or #17 and the attempt counter is equal to 5 for CS/PS mode 2 UE, TRACKING AREA UPDATE ACCEPT with EMM cause #16 or #17 and the attempt counter is equal to 5 for CS/PS mode 1 UE with "IMS voice not available" and with a persistent EPS bearer context, or TRACKING AREA UPDATE ACCEPT with EMM cause #22, as described in subclause 5.5.3.3.4.3.

ATTACH ACCEPT and the attempt counter is equal to 5 as described in subclause 5.5.1.2.4A and 5.5.1.2.6A.

TRACKING AREA UPDATE ACCEPT and the attempt counter is equal to 5 as described in subclause 5.5.3.2.4A and 5.5.3.2.6A.

DETACH REQUEST with other EMM cause values than those treated in subclause 5.5.2.3.2 or no EMM cause IE and Detach type IE indicates "re-attach not required" as described in subclause 5.5.2.3.4.

ATTACH REQUEST sent

TRACKING AREA UPDATE REQUEST sent

NAS signalling connection released

 

Initiation of the attach procedure, if still required or TAU procedure

T3410

15s
NOTE 7
NOTE 8

In WB-S1/CE mode, 85s

EMM-REGISTERED-INITIATED

ATTACH REQUEST sent

ATTACH ACCEPT received

ATTACH REJECT received

Start T3411 or T3402 as described in subclause 5.5.1.2.6

T3411

10s

EMM-DEREGISTERED. ATTEMPTING-TO-ATTACH

 

EMM-REGISTERED. ATTEMPTING-TO-UPDATE

 

EMM-REGISTERED. NORMAL-SERVICE

At attach failure due to lower layer failure, T3410 timeout or attach rejected with other EMM cause values than those treated in subclause 5.5.1.2.5.

 

At tracking area updating failure due to lower layer failure, T3430 timeout or TAU rejected with other EMM cause values than those treated in subclause 5.5.3.2.5.

ATTACH ACCEPT and the attempt counter is less than 5 as described in subclause 5.5.1.2.4A and 5.5.1.2.6A.

TRACKING AREA UPDATE ACCEPT and the attempt counter is less than 5 as described in subclause 5.5.3.2.4A and 5.5.3.2.6A.

ATTACH REQUEST sent

TRACKING AREA UPDATE REQUEST sent

EMM-CONNECTED mode entered (NOTE 6)

Retransmission of the ATTACH REQUEST, if still required as described in subclause 5.5.1.2.6 or retransmission of TRACKING AREA UPDATE REQUEST

T3412

Default 54 min.

NOTE 2

NOTE 5

EMM-REGISTERED

In EMM-REGISTERED, when EMM-CONNECTED mode is left.

When entering state EMM-DEREGISTERED or when entering EMM-CONNECTED mode.

Initiation of the periodic TAU procedure if the UE is not attached for emergency bearer services or T3423 started under the conditions as specified in subclause 5.3.5.

 

Implicit detach from network if the UE is attached for emergency bearer services.

 

T3416

30s
NOTE 7
NOTE 8

In WB-S1/CE mode, 48s

EMM-REGISTERED-INITIATED

EMM-REGISTERED

EMM-DEREGISTERED-INITIATED

EMM-TRACKING-AREA-UPDATING-INITIATED

EMM-SERVICE-REQUEST-INITIATED

RAND and RES stored as a result of an EPS authentication challenge

SECURITY MODE COMMAND received

SERVICE REJECT received

SERVICE ACCEPT received

TRACKING AREA UPDATE ACCEPT received

AUTHENTICATION REJECT received

AUTHENTICATION FAILURE sent

EMM-DEREGISTERED, EMM-NULL or

EMM-IDLE mode entered

Delete the stored RAND and RES

T3417

5s
NOTE 7
NOTE 8

In WB-S1/CE mode, 51s

EMM-SERVICE-REQUEST-INITIATED

SERVICE REQUEST sent

EXTENDED SERVICE REQUEST sent in case f, g, i and j in subclause 5.6.1.1

EXTENDED SERVICE REQUEST sent with service type set to "packet services via S1" in case a, b, c, h and k in subclause 5.6.1.1

CONTROL PLANE SERVICE REQUEST sent as specified in subclause 5.6.1.2.2

Bearers have been set up

SERVICE REJECT received

SERVICE ACCEPT received

Indication of system change from lower layer received

cdma2000® 1xCS fallback rejection received

see subclause 5.6.1.4.2

Abort the procedure

T3417ext

10s

EMM-SERVICE-REQUEST-INITIATED

EXTENDED SERVICE REQUEST sent in case d in subclause 5.6.1.1

 

Inter-system change from S1 mode to A/Gb mode or Iu mode is completed

Inter-system change from S1 mode to A/Gb mode or Iu mode is failed

SERVICE REJECT received

Select GERAN or UTRAN

T3417ext-mt

4s

EMM-SERVICE-REQUEST-INITIATED

EXTENDED SERVICE REQUEST sent in case e in subclause 5.6.1.1 and the CSFB response was set to "CS fallback accepted by the UE"

Inter-system change from S1 mode to A/Gb mode or Iu mode is completed

Inter-system change from S1 mode to A/Gb mode or Iu mode is failed

SERVICE REJECT received

Select GERAN or UTRAN

T3418

20s
NOTE 7
NOTE 8

In WB-S1/CE mode, 38s

EMM-REGISTERED-INITIATED

EMM-REGISTERED

EMM-TRACKING-AREA-UPDATING-INITIATED

EMM-DEREGISTERED-INITIATED

EMM-SERVICE-REQUEST-INITIATED

AUTHENTICATION FAILURE (EMM cause = #20 "MAC failure" or #26 "non-EPS authentication unacceptable") sent

AUTHENTICATION REQUEST received or AUTHENTICATION REJECT received

or

SECURITY MODE COMMAND received

 

when entering EMM-IDLE mode

 

indication of transmission failure of AUTHENTICATION FAILURE message from lower layers

On first expiry, the UE should consider the network as false and follow item f of subclause 5.4.2.7, if the UE is not attached for emergency bearer services or access to RLOS.

 

On first expiry, the UE will follow subclause 5.4.2.7 under "For items c, d, and e:", if the UE is attached for emergency bearer services or if the UE is attached for access to RLOS.

T3420

15s
NOTE 7
NOTE 8

In WB-S1/CE mode, 33s

EMM-REGISTERED-INITIATED

EMM-REGISTERED

EMM-DEREGISTERED-INITIATED

EMM-TRACKING-AREA-UPDATING-INITIATED

EMM-SERVICE-REQUEST-INITIATED

AUTHENTICATION FAILURE (cause = #21 "synch failure") sent

AUTHENTICATION REQUEST received or AUTHENTICATION REJECT received

or

SECURITY MODE COMMAND received

 

when entering EMM-IDLE mode

 

indication of transmission failure of AUTHENTICATION FAILURE message from lower layers

On first expiry, the UE should consider the network as false and follow item f of subclause 5.4.2.7, if the UE is not attached for emergency bearer services or access to RLOS.

 

On first expiry, the UE will follow subclause 5.4.2.7 under "For items c, d, and e:", if the UE is attached for emergency bearer services or if the UE is attached for access to RLOS.

T3421

15s

NOTE 7

NOTE 8

In WB-S1/CE mode, 45s

EMM-DEREGISTERED-INITIATED

EMM-
REGISTERED.
IMSI-DETACH-
INITIATED

DETACH REQUEST sent with

the Detach type IE not indicating "switch off"

DETACH ACCEPT received

Retransmission of DETACH REQUEST

T3423

NOTE 3

EMM-REGISTERED

T3412 expires while ISR is activated and either T3346 is running or the UE is in one of the following states:

– EMM-REGISTERED.NO-CELL-AVAILABLE;

– EMM-REGISTERED.PLMN-SEARCH;

–EMM-REGISTERED.UPDATE-NEEDED; or

–EMM-REGISTERED.LIMITED-SERVICE.

When entering state EMM-DEREGISTERED or when entering EMM-CONNECTED mode.

Set TIN to "P‑TMSI".

For A/Gb mode or Iu mode, see 3GPP TS 24.008 [13]

 

T3430

15s
NOTE 7
NOTE 8

In WB-S1/CE mode, 77s

EMM-TRACKING-AREA-UPDATING-INITIATED

TRACKING AREA UPDATE REQUEST sent

TRACKING AREA UPDATE ACCEPT received

TRACKING AREA UPDATE REJECT received

Start T3411 or T3402 as described in subclause 5.5.3.2.6

T3440

10s

EMM-DEREGISTERED EMM-REGISTERED

 

ATTACH REJECT, DETACH REQUEST, TRACKING AREA UPDATE REJECT with any of the EMM cause #3, #6, #7, #8, #11, #12, #13, #14, #15, #25, #31 or #35

SERVICE REJECT received with any of the EMM cause #3, #6, #7, #8, #11, #12, #13, #15, #25, #31, #35 or #39

TRACKING AREA UPDATE ACCEPT received after the UE sent TRACKING AREA UPDATE REQUEST in EMM-IDLE mode without the "active" flag set and without the "signalling active" flag set, and the user-plane radio bearers have not been setup

DETACH ACCEPT received after the UE sent DETACH REQUEST with detach type to "IMSI detach"

Upon receipt of ESM DATA TRANSPORT message as described in subclause 5.3.1.2.1 (NOTE 9)

AUTHENTICATION REJECT received

NAS signalling connection released

Bearers have been set up or a request for PDN connection for emergency bearer services or a CS emergency call is started

Upon receipt of ESM DATA TRANSPORT message as described in subclause 5.3.1.2.1 (NOTE 9)

Release the NAS signalling connection for the cases a), b) and c) as described in subclause 5.3.1.2

EMM-DEREGISTERED

EMM-DEREGISTERED.NORMAL-SERVICE

TRACKING AREA UPDATE REJECT, SERVICE REJECT with any of the EMM cause #9, #10 or #40

NAS signalling connection released

 

Release the NAS signalling connection for the cases d) and e) as described in subclause  5.3.1.2 and initiation of the attach procedure as specified in subclause 5.5.3.2.5, 5.5.3.3.5 or 5.6.1.5

T3442

NOTE 4

EMM-REGISTERED

SERVICE REJECT received with EMM cause #39 "CS service temporarily not available" with a non-zero T3442 value

TRACKING AREA UPDATE REQUEST sent

None

T3444

NOTE 11

All except EMM-NULL and 5GMM-NULL (defined in 3GPP TS 24.501 [54])

– UE configured for eCall only mode enters EMM-IDLE mode after an eCall over IMS

– UE configured for eCall only mode moves from GERAN/UTRAN to E-UTRAN with timer T3242 (see 3GPP TS 24.008 [13]) running

– UE configured for eCall only mode enters 5GMM-IDLE mode (defined in 3GPP TS 24.501 [54]) after an eCall over IMS

– Removal of eCall only restriction

– Intersystem change from S1 mode to A/Gb or Iu mode

Perform eCall inactivity procedure in EPS as described in subclause 5.5.4.

Perform eCall inactivity procedure in 5GS as described in 3GPP TS 24.501 [54].

T3445

NOTE 12

All except EMM-NULL and 5GMM-NULL (defined in 3GPP TS 24.501 [54])

– UE configured for eCall only mode enters EMM-IDLE mode after a call to a non-emergency MSISDN or URI for test or terminal reconfiguration service

– UE configured for eCall only mode moves from GERAN/UTRAN to E-UTRAN with timer T3243 (see 3GPP TS 24.008 [13]) running

– UE configured for eCall only mode enters 5GMM-IDLE mode (defined in 3GPP TS 24.501 [54]) after a call to a non-emergency MSISDN or URI for test or terminal reconfiguration service

Removal of eCall only restriction

– Intersystem change from S1 mode to A/Gb or Iu mode

Perform eCall inactivity procedure in EPS as described in subclause 5.5.4.

Perform eCall inactivity procedure in 5GS as described in 3GPP TS 24.501 [54].

T3447

NOTE 2

All except EMM-NULL

NAS signalling connection release that was not established for paging, attach without PDN connection or tracking area update request without "active" or "signalling active" flag set.

N1 NAS signalling connection release that was not established due to paging, or REGISTRATION REQUEST for initial registration with Follow-on request indicator set to "No follow-on request pending", or REGISTRATION REQUEST for mobility and periodic registration update with Follow-on request indicator set to "No follow-on request pending" and without Uplink data status IE included (defined in 3GPP TS 24.501 [54]).

ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT without the T3447 value IE.

Inter-system change from S1 mode to A/Gb mode or Iu mode is completed

REGISTRATION ACCEPT without the T3447 value IE (defined in 3GPP TS 24.501 [54]). CONFIGURATION UPDATE COMMAND with the T3447 value IE set to zero or deactivated (defined in 3GPP TS 24.501 [54]).

Allowed to initiate transfer of uplink user data

T3448

NOTE 10

All except EMM-NULL and 5GMM-NULL (defined in 3GPP TS 24.501 [54])

ATTACH ACCEPT message or TRACKING AREA UPDATE ACCEPT message or SERVICE ACCEPT message received with a non-zero T3448 value.

SERVICE REJECT message received with EMM cause #22 "Congestion" and a non-zero T3448 value.

REGISTRATION ACCEPT message or SERVICE ACCEPT message received with a non-zero T3448 value(defined in 3GPP TS 24.501 [54])

SERVICE REJECT message received with 5GMM cause #22 "Congestion" and a non-zero T3448 value(defined in 3GPP TS 24.501 [54])

SERVICE ACCEPT message or TRACKING AREA UPDATE ACCEPT message received without T3448 value

SERVICE ACCEPT message or REGISTRATION ACCEPT message received without T3448 value(defined in 3GPP TS 24.501 [54])

 

Allowed to initiate transfer of user data via the control plane

T3449

5s

NOTE 7
NOTE 8

In WB-S1/CE mode, 51s

EMM-REGISTERED

Bearers have been set up

SECURITY MODE COMMAND message received

 

SERVICE ACCEPT message received

Security protected ESM message or a security protected EMM message not related to an EMM common procedure received

SERVICE ACCEPT message considered as a protocol error and EMM STATUS returned

NOTE 1: The cases in which the default value of this timer is used are described in subclause 5.3.6.

NOTE 2: The value of this timer is provided by the network operator during the attach and tracking area updating procedures.

NOTE 3: The value of this timer may be provided by the network in the ATTACH ACCEPT message and TRACKING AREA UPDATE ACCEPT message. The default value of this timer is identical to the value of T3412.

NOTE 4: The value of this timer is provided by the network operator when a service request for CS fallback is rejected by the network with EMM cause #39 "CS service temporarily not available".

NOTE 5: The default value of this timer is used if the network does not indicate a value in the TRACKING AREA UPDATE ACCEPT message and the UE does not have a stored value for this timer.

NOTE 6: The conditions for which this applies are described in subclause 5.5.3.2.6.

NOTE 7: In NB-S1 mode, the timer value shall be calculated as described in subclause 4.7.

NOTE 8: In WB-S1 mode, if the UE supports CE mode B and operates in either CE mode A or CE mode B, then the timer value is as described in this table for the case of WB-S1/CE mode (see subclause 4.8).

NOTE 9: It is possible that the UE does not stop or start timer T3440 upon receipt of ESM DATA TRANSPORT message as described in subclause 5.3.1.2.1.

NOTE 10: The timer value is provided by the network in the ATTACH ACCEPT, TRACKING AREA UPDATE ACCEPT, SERVICE ACCEPT, SERVICE REJECT or REGISTRATION ACCEPT message, or chosen randomly from a default value range of 15 – 30 minutes.

NOTE 11: If the timer is started due to a UE configured for eCall only mode moving from GERAN/UTRAN to E-UTRAN with timer T3242 (see 3GPP TS 24.008 [13]) running, the UE starts the timer with a value set to the time left on timer T3242. Otherwise the UE starts the timer with a value set to 12 hours.

NOTE 12: If the timer is started due to a UE configured for eCall only mode moving from GERAN/UTRAN to E-UTRAN with timer T3243 (see 3GPP TS 24.008 [13]) running, the UE starts the timer with a value set to the time left on timer T3243. Otherwise the UE starts the timer with a value set to 12 hours.

 

The post EPS Mobility Management Timers – UE side appeared first on Telecompedia.

]]>
https://telecompedia.net/eps-mobility-management-timers-ue-side/feed/ 0
EPS Mobility Management Timers – Network side https://telecompedia.net/eps-mobility-management-timers-network-side/ https://telecompedia.net/eps-mobility-management-timers-network-side/#respond Wed, 15 Jul 2020 06:13:58 +0000 http://telecompedia.net/?p=508 EPS mobility management timers – network side TIMER NUM. TIMER VALUE STATE CAUSE OF START NORMAL STOP ON THE 1st, 2nd, 3rd, 4th EXPIRY (NOTE 1) T3413 NOTE 8 NOTE 10 NOTE 2 EMM-REGISTERED Paging procedure for EPS services initiated Paging procedure for EPS services completed Paging procedure READ MORE

The post EPS Mobility Management Timers – Network side appeared first on Telecompedia.

]]>
Following table is from 3GPP 24.301 which presents description of LTE EPS Mobility Management Timers at network side: T3413; T3415; T3422; T3447; T3450; T3460; T3470; Implicit detach, Mobile reachable

EPS mobility management timers – network side

TIMER NUM.

TIMER VALUE

STATE

CAUSE OF START

NORMAL STOP

ON THE
1st, 2nd, 3rd, 4th EXPIRY (NOTE 1)

T3413
NOTE 8
NOTE 10

NOTE 2

EMM-REGISTERED

Paging procedure for EPS services initiated

Paging procedure for EPS services completed

Paging procedure is aborted

Network dependent

T3415
NOTE 8
NOTE 10

NOTE 6

EMM-REGISTERED

Paging procedure for EPS services initiated for a UE which the network accepted the request to use eDRX and the UE does not have a PDN connection for emergency bearer services

Paging procedure for EPS services completed

Paging procedure is aborted

Paging procedure is aborted and the network proceeds as specified in 3GPP TS 23.401 [10]

T3422
NOTE 7
NOTE 9

6s

In WB-S1/CE mode, 24s

EMM-DEREGISTERED-INITIATED

DETACH REQUEST sent

DETACH ACCEPT received

Retransmission of DETACH REQUEST

T3447

NOTE 2

All

UE transitions from EMM-CONNECTED mode to EMM-IDLE mode except when UE was in EMM-CONNECTED mode due to paging, attach without PDN connection or tracking area update request without "active" or "signalling active" flag set

UE transitions from 5GMM-CONNECTED mode to 5GMM-IDLE mode except when UE was in 5GMM-CONNECTED mode due to paging, REGISTRATION REQUEST for initial registration with Follow-on request indicator set to "No follow-on request pending", or REGISTRATION REQUEST for mobility and periodic registration update with Follow-on request indicator set to "No follow-on request pending" and without Uplink data status IE included.

ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT without the T3447 value IE. At MME during inter-system change from S1 mode to N1 mode.

REGISTRATION ACCEPT without the T3447 value IE (defined in 3GPP TS 24.501 [54]). CONFIGURATION UPDATE COMMAND with the T3447 value IE set to zero or deactivated (defined in 3GPP TS 24.501 [54]). At AMF during inter-system change from N1 mode to S1 mode defined in 3GPP TS 24.501 [54]).

Allow the UE to initiate a connection for transfer of uplink user data.

T3450
NOTE 7
NOTE 9

6s

In WB-S1/CE mode, 18s

EMM-COMMON-PROC-INIT

ATTACH ACCEPT sent

 

TRACKING AREA UPDATE ACCEPT sent with GUTI

 

TRACKING AREA UPDATE ACCEPT sent with TMSI

 

GUTI REALLOCATION COMMAND sent

ATTACH COMPLETE received

TRACKING AREA UPDATE COMPLETE received

GUTI REALLOCATION COMPLETE received

Retransmission of the same message type, i.e. ATTACH ACCEPT, TRACKING AREA UPDATE ACCEPT or GUTI REALLOCATION COMMAND

T3460
NOTE 7
NOTE 9

6s

In WB-S1/CE mode, 24s

EMM-COMMON-PROC-INIT

AUTHENTICATION REQUEST sent

 

SECURITY MODE COMMAND sent

AUTHENTICATION RESPONSE received

AUTHENTICATION FAILURE received

SECURITY MODE COMPLETE received

SECURITY MODE REJECT received

Retransmission of the same message type, i.e. AUTHENTICATION REQUEST

or SECURITY MODE COMMAND

T3470
NOTE 7
NOTE 9

6s

In WB-S1 mode, 24s

EMM-COMMON-PROC-INIT

IDENTITY REQUEST sent

IDENTITY RESPONSE received

Retransmission of IDENTITY REQUEST

Mobile reachable

NOTE 4

All except EMM-DEREGISTERED

Entering EMM-IDLE mode

NAS signalling connection established

Network dependent, but typically paging is halted on 1st expiry if the UE is not attached for emergency bearer services.

 

Implicitly detach the UE which is attached for emergency bearer services.

Implicit detach timer

NOTE 3

All except EMM-DEREGISTERED

The mobile reachable timer expires while the network is in EMM-IDLE mode

NAS signalling connection established

Implicitly detach the UE on 1st expiry

active timer

NOTE 5

All except EMM-DEREGISTERED

Entering EMM-IDLE mode

NAS signalling connection established

Network dependent, but typically paging is halted on 1st expiry

NOTE 1:   Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description.

NOTE 2:   The value of this timer is network dependent.

NOTE 3:   The value of this timer is network dependent. If ISR is activated, the default value of this timer is 4 minutes greater than T3423.

NOTE 4:   The default value of this timer is 4 minutes greater than T3412. If T3346 is larger than T3412 and the MME includes timer T3346 in the TRACKING AREA UPDATE REJECT message or SERVICE REJECT message, the value of the mobile reachable timer and implicit detach timer is set such that the sum of the timer values is greater than T3346. If the UE is attached for emergency bearer services, the value of this timer is set equal to T3412.

NOTE 5:   If the MME includes timer T3324 in the ATTACH ACCEPT message or TRACKING AREA UPDATE ACCEPT message and if the UE is not attached for emergency bearer services and has no PDN connection for emergency bearer services, the value of this timer is equal to the value of timer T3324.

NOTE 6:   The value of this timer is smaller than the value of timer T3-RESPONSE (see 3GPP TS 29.274 [16D]).

NOTE 7:   In NB-S1 mode, then the timer value shall be calculated as described in subclause 4.7.

NOTE 8:   In NB-S1 mode, then the timer value shall be calculated by using an NAS timer value which is network dependent.

NOTE 9:   In WB-S1 mode, if the UE supports CE mode B and operates in either CE mode A or CE mode B, then the timer value is as described in this table for the case of WB-S1/CE mode (see subclause 4.8).

NOTE 10: In WB-S1 mode, if the UE supports CE mode B, then the timer value shall be calculated by using an NAS timer value which value is network dependent.

 

 

The post EPS Mobility Management Timers – Network side appeared first on Telecompedia.

]]>
https://telecompedia.net/eps-mobility-management-timers-network-side/feed/ 0