LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

LTE FDD Release RL30 Features Part 1

RL10 development has been focused in providing high speed broadband access and
introduction of Self-Organising Network (SON). Based on field trial, a Flexi Multiradio LTE
BTS is capable of delivering nearly 100 Mbps of maximum DL cell throughput and nearly
50 Mbps of maximum UL cell throughput, both are measured on TCP level, 20 MHz of
system bandwidth and 4 x cat3 UEs. RL10 is also a breakthrough in network management
system by introducing Auto-connection and Auto-configuration as part of SON features.
RL20 development is focused in providing Quality of Service (QoS) and flexibility in
network implementation. QoS implementation enables operators to provide guaranteed
service (e.g. Voice over LTE) and service differentiation for their customer. RL20 also
enables flexibility in network implementation; e.g. more frequency bands are supported,
Flexi Multiradio RF module sharing with GSM, more option for LTE system bandwidth etc.
In general, RL20 content are:
Enhancement in LTE QoS
Enables commercial VoLTE operation
Enhancement in SON functions
Enables additional backhaul configurations
Extends the supported site solutions and frequency variants

RA41401EN04GLA1

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

LTE FDD Release RL30 Features Part 1

Support of emergency calls, lawful interception and location based charging.

RA41401EN04GLA1

10

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

11

LTE FDD Release RL30 Features Part 1

During setup of S1-link, MME configuration information is downloaded to eNB

(e.g. Relative MME Capacity, Served PLMNs, MME-Name)
If the operator modifies the MME configuration information for an existing S1-link, the eNB has to be
informed about these changes
For this purpose, 3GPP has defined the MME Configuration Update procedure
Without support of MME Configuration Update (i.e. without LTE450), the S1 has to be closed and
afterwards re-established again in order to update the S1 link configuration information
stored in eNB.
Note: If S1-link is closed, all UE connections using the link have to be released.

GUTI = GUMMEI + M-TMSI, where

GUMMEI = MCC + MNC + MME Identifier and
MME Identifier = MME Group ID + MME Code
MCC and MNC shall have the same field size as in earlier 3GPP systems.
M-TMSI shall be of 32 bits length.
MME Group ID shall be of 16 bits length.
MME Code shall be of 8 bits length.
GUTI - Globally Unique Temporary UE Identity
GUMMEI - Globally Unique MME Identifier
MMEGI - MME Group ID
MMEC - MME Code
S-TMSI = SAE Temporary Mobile Subscriber Identity
M-TMSI = MME Temporary Mobile Subscriber Identity

RA41401EN04GLA1

12

LTE FDD Release RL30 Features Part 1

S1 Partial Reset
Is a service procedure which allows to perform a 'bulk release' of many UE-associated
S1-signaling connections available on a S1 link with one message exchange
between eNB and MME.
RRC connections of UEs impacted by the S1 Partial Reset (if available) are released by
eNB.
All S1-i/f related resources are released
(including also GTP-U interface in S-GW)
S1 Partial Reset may be triggered either by eNB or by MME
Functional Description: The partial S1 reset can be initiated by the eNode B or the MME
with the
S1AP:RESET message.
The indicated logical resources are released and the reset is acknowledged by a
S1AP:RESET
ACKNOWLEDGE message.
The Flexi Multiradio BTS is able to handle multiple S1 partial reset procedures per S1 link
in parallel.
The Flexi Multiradio BTS releases in addition related resources at the air interface via a
RRC:RRC
CONNECTION RELEASE message.

RA41401EN04GLA1

13

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

14

LTE FDD Release RL30 Features Part 1

Disabled feature allows still emergency sessions, but they will be handled as normal
sessions (no prioritization, usual mobility).
An emergency session will be assumed, if
RRC establishment has cause "emergency", or
there is at least one bearer with emergency ARP.
Note: Emergency ARP is an eNB locally defined ARP value. If a bearer ARP matches it,
this bearer is assumed to be for emergency purposes.

RA41401EN04GLA1

15

LTE FDD Release RL30 Features Part 1

Mobility is limited.
No inter PLMN mobility
Intra LTE fully supported
same MSC, but handover restrictions from MME are ignored
admittance is prioritized like session setup
IRAT only by connection release with redirect
redirection targets from LTE22 or LTE562 or LTE432
SRVCC shall be added later, but is not part for RL30

RA41401EN04GLA1

16

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

17

LTE FDD Release RL30 Features Part 1

DRX disabled:
UE always monitors PDCCH for UL and DL grants.
DRX enabled:
Timeline is divided in DRX cycles of same number of subframes, one DRX cycle
after another.
Start of DRX cycle is linked to SFN + offset.
There are certain periods within a DRX cycle when a UE is DRX Active.
If a UE is DRX Active, it monitors the PDCCH for UL and DL grants.
When a UE is DRX Sleep (i.e. not DRX Active), CQI/SRS/PMI/RI shall not be
reported.
A UE is DRX Active (= Active Time) according to TS 36.321 (5.7), if
the On Duration Timer or the DRX Inactivity Timer or a DRX Retransmission
Timer or the Contention Resolution Timer is running,
a Scheduling Request sent on PUCCH is pending,
an uplink grant for a pending HARQ retransmission can occur,
a PDCCH (allocation) indicating a new transmission addressed to the C-RNTI of
the UE has not been received after successful reception of a Random Access
Response for the explicitely signalled preamble.
TTI in LTE 1ms transmission time interval.

RA41401EN04GLA1

18

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

19

LTE FDD Release RL30 Features Part 1

DRX Profile 101 (drxProfile101)

It defines the DRX profile to be used by the UE when doing intra-frequency
ReportCGI measurements. Cycle size offers following range of values: {40; 80; 160}
ms. Below 160 ms, no out of sync handling is required, i.e. LTE473 features are not
needed

RA41401EN04GLA1

20

LTE FDD Release RL30 Features Part 1

In LTE, when UE wish to establish RRC connection with eNB, it transmits a Random
Access Preamble, eNB estimates the transmission timing of the terminal based on this.
Now eNB transmits a Random Access Response which consists of timing advance
command, based on that UE adjusts the terminal transmit timing.

RA41401EN04GLA1

21

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

22

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

23

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

24

LTE FDD Release RL30 Features Part 1

The introduction of operator specific QCIs requires an alignment with the EPC.

RA41401EN04GLA1

25

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

26

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

27

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

28

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

29

LTE FDD Release RL30 Features Part 1

101 profiles for QCI 1

The following setting aplies to radio interface
Qci, QoS Class Identifier.
resType, The Resource Type indicates whether bearer is a GBR or NON-GBR bearer.
Prio, This parameter gives the priority of the EPS bearer according TS23.203. QCI 1
priority = 2, QCI 5 priority = 1.
qciSupp, Indicates whether the given QCI is supported and enabled.
rlcMode, Configures the RLC Mode of the data radio bearer. QCI 1 mode is RLC_UM and
QCI 5 mode is RLC_AM.
rlcProfIdx, Specifies the ID of the corresponding RLC profile. QCI 1 profile is 101 and QCI
5 profile is {1,2,3, default:1}
pdcpProfIdx, Specifies the ID of the corresponding PDCP profile. QCI 1 profile is 101 and
QCI 5 profile is {1,2,3, default:1}
Dscp, configures the DSCP (Differentiated Services Code Point) value associated with the
QCI. Range: {1-63}, default QCI 1 is 46, default QCI 5 is 34.
schedulWeight, specifies the scheduling weight for eNB schedulers in case the delaybased prioritization is disabled. Range {1-100}, default QCI 1 is 40, default QCI 5 is 40.
schedulBSD, This parameter is used to configure the Bucket Size Duration (BSD) of the
UL scheduler
QCI 1 range: {50ms, 100ms, 150ms, 300ms, 500ms, 1000ms}, default: 100ms
QCI 5 range: {50ms, 100ms, 150ms, 300ms, 500ms, 1000ms}, default: 100ms
schedulPrio, Logical Channel Priority for the MAC scheduler. Range {2-16}, default QCI 1
is 5, default QCI 5 is 9.
Lcgid, Logical Channel Group Identifier for buffer status reporting. QCI 1 identifier = 1,
QCI 5 identifier = 2 {2,3}
delayTarget, Maximum packet delay value used by the eNB MAC scheduling algorithm.
Only applicable for QCI 1. Range: 50, 60, ,100ms, default: 80ms.

RA41401EN04GLA1

30

LTE FDD Release RL30 Features Part 1

The measurements events A2 and A1 are used to start and stop IRAT measurements and
can be configured by the operator.
The UE capabilities are considered as well for the setup of the IRAT measurement
configuration, e.g. support of measurement gap and support of frequency bands.
The target cells for the IRAT measurements can be configured by the operator.
Blacklisting of target cells is supported.
The event B2 is used for the IRAT measurements.
The measurement configuration as source cell thresholds (RSRP), target cell thresholds
(RSSI), hysteresis, time to trigger and speed dependent scaling can be configured by the
operator.

RA41401EN04GLA1

31

LTE FDD Release RL30 Features Part 1

The measurements events A2 and A1 are used to start and stop IRAT measurements and
can be configured by the operator.
The UE capabilities are considered as well for the setup of the IRAT measurement
configuration, e.g. support of measurement gap and support of frequency bands.
The target cells for the IRAT measurements can be configured by the operator.
Blacklisting of target cells is supported.
The event B2 is used for the IRAT measurements.
The measurement configuration as source cell thresholds (RSRP), target cell thresholds
(RSSI), hysteresis, time to trigger and speed dependent scaling can be configured by the
operator.

Requires feature Redirect LTE to other technologies (LTE _423) i.e. RRC Connection
Release with Redirect (RL10 feature): message is triggered based on source cell downlink
RSRP measurements (even A2)
A1: start A2:stop inter frequency measurements

RA41401EN04GLA1

32

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

33

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

34

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

35

LTE FDD Release RL30 Features Part 1

with NACC (Network Assisted Cell Change) because the system info of 2G target cell is
sent to the UE. This gives a gain ~1s but still the service interruption can be significant
(e.g. 6 sec in case of WCDMA-> GSM NCCR)
Measurements are triggered early enough to take to take the necessary actions on the UE
side (in contrast to triggering the RL10 redirection procedure performed in critical
conditions related to LTE coverage end without prior measurements of 2G/3G)

RA41401EN04GLA1

36

LTE FDD Release RL30 Features Part 1

B2 serving cell becomes worse than threshold and neighbour cell becomes better than
other threshold.

RA41401EN04GLA1

37

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

38

LTE FDD Release RL30 Features Part 1

T304 handover failure timer

RA41401EN04GLA1

39

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

40

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

41

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

42

LTE FDD Release RL30 Features Part 1

Support of Intra-Frequency cell individual offsets (CIO cell list) and Intra-Frequency
specific offsets
The eNB supports the configuration of Intra-Frequency Cell Individual Offsets (CIO) in the
CIO cell list in the measurement configuration of the serving carriers measurement object
for the A3 event (Neighbour becomes better than serving) and the A5 event (Coverage).
The CIO cell list is used to explicitly indicate to the UEs which cells/PCIs to measure with
an individual CIO to be applied for measurement events. The CIO cell list is compiled from
a parameter in LNCEL for the serving cell and from parameters in LNREL for other
neighbour cells
The eNB supports the configuration of frequency specific offsets in the measurement
configuration of the serving carriers measurement object (Intra) for the A3 event
(Neighbour becomes better than serving).
Support of Inter-Frequency cell individual offsets (CIO cell lists) and InterFrequency specific offsets
The eNB supports the configuration of Inter-Frequency Cell Individual Offsets (CIO) in the
CIO cell lists in the measurement configuration of the neighbour carriers measurement
objects for the A3 event (Neighbour becomes better than serving) and the A5 event
(Coverage).
The CIO cell list is used to explicitly indicate to the UEs which cells/PCIs to measure with
an individual CIO to be applied for measurement events. The CIO cell lists of neighbour
carriers is compiled from parameters in LNREL for other neighbour cells.
The eNB supports the configuration of frequency specific offsets in the measurement
configuration of the neighbour carriers measurement objects for the A3 event (Neighbour
becomes better than serving) and the A5 event (Coverage).

RA41401EN04GLA1

43

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

44

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

45

LTE FDD Release RL30 Features Part 1

Each 10-millisecond LTE frame represents 12288 CDMA2000 chips. When the bounder of
an LTE frame is synchronous with the CDMA2000 frame signal, the CDMA2000 system
time is broadcasted in SIB8. The difference in timing between the LTE frame and the
broadcasted CDMA2000 system time will remain between 1 microsecond.

RA41401EN04GLA1

46

LTE FDD Release RL30 Features Part 1

In RL30 following mobility types are supported within Mobility Profiles configuration:
Inter-frequency handover (LTE55)
Inter RAT handover to WCDMA (LTE56)
Network Assisted Cell Change to GSM (LTE442)
CSFB to UTRAN or GSM via redirect (LTE562)
RRC connection release with redirect (LTE423)
Emergency Call Handling (LTE22)
and will be enhanced in future with new mobility features.

RA41401EN04GLA1

47

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

48

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

49

LTE FDD Release RL30 Features Part 1

Default Profile (MOCs MODPR and MODRED)) must be manually created by operator on
NetAct (no automatic generation even if it is a copy of current configuration), but if operator
would like to use all existing LNHO* configuration a special flag (parameter autoAdapt ) is
enabled in this MOC

RA41401EN04GLA1

50

LTE FDD Release RL30 Features Part 1

However to use given mobility type with given SPID in mobility procedure, then feature
corresponding to mobility type must be enabled.
Setting of feature activation flags will not be checked with consistency check mechanism. If
mobility type is not enabled, then mobility type is not used.
It is possible to restrict all active Inter-frequency and Inter-RAT mobility for a given SPID ->
by configuring empty Mobility Profile (empty MOC MOPR).
Only Intra-frequency mobility will be possible for UE with such configuration of SPID and
assigned empty Mobility Profile.

RA41401EN04GLA1

51

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

52

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

53

LTE FDD Release RL30 Features Part 1

Mapping betwen Mobility Profile instance and Subscriber Profile ID value is done on cell
level in LNCEL object (parameter moPrMappingList). SPID value range is taken from
range restricted by 3GPP for operator use (1..128)
There could be multiple SPID values mapped to one profile.
Modification of O&M definitions of Mobility Profiles and mapping to SPID values will be
done online, but new configuration will be valid only for new UEs.

RA41401EN04GLA1

54

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

55

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

56

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

57

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

58

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

59

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

60

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

61

LTE FDD Release RL30 Features Part 1

The PCFICH (Physical Control Format Indicator Channel) provides information about the
number of OFDM symbols used for the PDCCH.
The Flexi Multiradio BTS supports dedicated power control settings for the PCFICH in
order to ensure that especially cell edge UEs can properly receive the PCFICH.
The downlink reference symbols are used by the UE for the channel estimation and used
for Cell Measurements (Level, Quality) for Handover purposes.
Physical Hybrid Automatic Repeat Request Indicator Channel - HARQ

RA41401EN04GLA1

62

LTE FDD Release RL30 Features Part 1

The information is broadcasted every TTI via PCFICH.

For good control channel performance different coding schemes

are necessary. As a result, each scheduling grant is defined based
on fixed size control channel elements (CCE) which are combined
in a predetermined manner to achieve different coding rates. Only
QPSK modulation is used so that only a small number of coding
formats have to be defined. Because multiple control channel elements
can be combined to effectively reduce effective coding
rate, a user control channel assignment would then be based
on channel quality information reported. A user then monitors
a set of candidate control channels which may be configured by
higher layer signaling. To minimize the number of blind decoding
attempts, 1, 2, 4, 8 CCEs may be aggregated, resulting in code
rates of approx 2/3, 1/3, 1/6, 1/12.

RA41401EN04GLA1

63

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

64

LTE FDD Release RL30 Features Part 1

PDCCH carries information about the resources assignments for both Uplink (UL) and
Downlink (DL) data channels.
If a PDCCH payload is missed the User Equipment (UE) cannot know whether it has been
scheduled and on which time/frequency resources

RA41401EN04GLA1

65

LTE FDD Release RL30 Features Part 1

PDCCH Inner Loop Link (ILLA) adaptation is based on the Wideband CQI
measurement; this value is known to be affected by errors when assuming a realistic
system:
Wideband CQI measurement and quantization errors and delay
Uncertain mapping from CQI to required PDCCH format
the CQI calculation depends on the actual UE implementation while the mapping
table is based on assumptions in link simulations
the CQI is measured on the Data Channel (PDSCH) by the Data Channel
receiver assuming 10% BLER target, while the PDCCH is decoded potentially by
a different receiver
Uncertain mapping from WB-CQI that is a wideband averaging and the effective
SINR experienced from the user that depends only on those subcarriers on which
the PDCCH payload transmission is actually done

The PDCCH OLLA is needed to compensate for those various imperfections in the
PDCCH ILLA by dynamically adjusting the channel quality estimation per user

RA41401EN04GLA1

66

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

67

LTE FDD Release RL30 Features Part 1

Measurements done on PUSCH subspecrtums.

RA41401EN04GLA1

68

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

69

LTE FDD Release RL30 Features Part 1

P0 is a user specific parameter related to avarage received SINR.

PHR report containing power on which UE is working.

RA41401EN04GLA1

70

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

71

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

72

LTE FDD Release RL30 Features Part 1

Furthermore, should Sounding Reference Symbol (SRS) be enabled, support for MCS24
needs to be disabled on a cell basis to avoid code rate exceeding 1.
MCS24 shall only be applied for PUSCH allocations > 9 PRBs to avoid cases where
inband signaling of CQI, dyn. ACK/NACK etc. would lead to code rate exceeding 1.

With 20 MHz, totally 100 RBs can be used for DL and UL. In UL, min 2 RBs need to be
reserved for PUCCH. Thus, the max number of PRBs that can be allocated to PUSCH of a
single UE falls back to 96 as PUSCH allocation need to be a multiple of 2, 3 and/or 5. Max
number of PRBs to be allocated in other bandwidths can be derived accordingly.
Additionally for 10 MHz case, it is required to support a configuration with 2 PRBs PUCCH
and max 48 PRBs for PUSCH.

RA41401EN04GLA1

73

LTE FDD Release RL30 Features Part 1

RA41401EN04GLA1

74