Académique Documents
Professionnel Documents
Culture Documents
Contents
Field KPI
Multi-Carrier operation and CA VoLTE and other GBR services How to cope with traffic growth?
99.00% 96.07%
0.10% 1.95%
98.50% 93.40%
S B
System Selection/Registration
Information on USIM HPLMN on RAT basis CSG Identities list Forbidden PLMN list RPLMN etc
Information on ME UE Category, RAT support Frequency band Forbidden PLMNs/TAs/Las MRU Acquisition information Barred Cells/Barred Frequencies etc
* Qualcomm
RRC AS
(6) Process SIB1 Check PLMN Is Cell reserved? Is CSG Id valid? Cell belong to Forbidden TA? Cell barred? If fail, go back to (3). If ok, go to (7).
PHY
Types of Services
Normal: Receive Paging and can transition to Connected state Limited**: Emergency calls and ETWS Operator: For operators only on reserved cell
* Cell that is Acceptable to one UE can be a Suitable for another UE and vice versa. ** UE in Limited Service periodically scans system to obtain Normal Service
UE-associated signaling connection across the S1_MME called UE-associated logical S1connection (in MME)
RRC Connection
RRC Connection established
RRC-Idle
RRC Connection released
RRC-connected
RRC-Idle
A UE specific DRX may be configured by upper layers. UE controlled mobility; (Cell selection/reselection, TA update) The UE: Monitors a Paging channel to detect incoming calls, system information change, for ETWS capable UEs, ETWS notification, and for CMAS capable UEs, CMAS notification; Performs neighbouring cell measurements and cell (re-)selection; Acquires system information. Transfer of unicast data to/from UE. At lower layers, the UE may be configured with a UE specific DRX. Network controlled mobility, i.e. handover; The UE: Monitors a Paging channel and/ or System Information Block Type 1 contents to detect system information change, for ETWS capable UEs, ETWS notification, and for CMAS capable UEs, CMAS notification; Monitors control channels associated with the shared data channel to determine if data is scheduled for it; Provides channel quality and feedback information; Performs neighbouring cell measurements and measurement reporting; Acquires system information.
RRC-Connected
Random Access
Objectives of random access
Get unique UE identity (C-RNTI) Timing correction information for uplink
DL data arrival during RRC_CONNECTED requiring RA procedure when UL synchronization status is non-synchronised
is non-synchronised or there is no PUCCH resources for SR
PRACH
PRACH RA preamble 6RB 1.25kHz (format #4 7.5kHz) 64 preamble sequences for each cell 64 random access opportunities per PRACH resource Sequence 839 Z-C sequence (format #4 139)
Phase modulation: Due to the ideal auto-correlation property, there is no intra-cell interference from multiple random access attempt using preambles derived from the same Z-C root sequence. Higher layers control the preamble format
(~15km)
(~100km)
SINR sequence repetition (~30km) SINR sequence repetition (~100km) TDD
PRACH Location
One PRACH resource of 6 RBs per subframe (for FDD) Multiple UEs can access same PRACH resource by using different preambles PRACH may or may not present in every subframe and every frame PRACH-Configuration-Index parameter indicates frame number and subframe numbers where the PRACH resource is available. Starting frequency is specified by the network ( ) No frequency hopping for PRACH
There is probability that multiple UEs in the cell could pick the same
preamble signature and the eNB would assign the same PRB to both UEs for UL transmission of message/data
1)
2)
Contention Resolution
PDSCH
Only the first step uses physical-layer processing specifically designed for RA If UE has been requested to perform a contention-free random access (e.g. handover
to a new cell), the preamble to use is explicitly indicated from eNB
For FDD, there is at most one random-access region per subframe Power Ramp (with time backoff) can be applied until preamble is received
Collision when multiple UEs using the same preamble at the same time at Step 1.
In this case, multiple UEs will react upon the same downlink response message and collision occurs.
Each UE receiving the downlink message will compare the Contention Resolution ID Only one UE which observes a match b/w the ID received in Step 4 and the ID (CCCH
SDU) used in Step 3 will declare the random-access procedure successful.
The timer will expire for the other UEs for them to restart the RA process
TTA LTE/MIMO Standards/Technology Training 24 Nokia Siemens Networks
Timing Advance
LTE Handover
LTE uses hard handover LTE uses UE-assisted network controlled handover
UE reports measurements;
network decides when handover and to which Cell frequency need to be indicated
Buffered and new data is transferred from source to target eNB until path switch UE uses contention-free random access to accelerate handover
UTRA metrics
UTRA FDD CPICH RSCP UTRA FDD carrier RSSI UTRA FDD CPICH Ec/No
GSM metrics
GSM carrier RSSI
CDMA2000 metrics
CDMA2000 1xRTT pilot strength CDMA2000 HRPD pilot strength
Periodical Reporting
Report strong cells periodically regardless, if configured by network
TTA LTE/MIMO Standards/Technology Training 28 Nokia Siemens Networks
Inter-eNB Handover
2. The source eNodeB issues a HANDOVER REQUEST message via the X2 interface to the
target eNodeB which passes necessary information to prepare the handover at the target side. This message includes signalling references, transport layer addresses and tunnel endpoint identifiers to enable the target eNodeB to communicate with the source eNodeB and the EPC nodes, as well as QoS information for the UE's bearers and RRM information.
3. Admission Control is performed by the target eNodeB dependent on the received radio
bearer QoS information and S1 connectivity to increase the likelihood of a successful handover. If the resources can be granted by the target eNodeB, it configures the required resources according to the received UE context information, and reserves a C-RNTI (cell radio network temporary identifier) and a dedicated preamble for the UE.
4. The target eNodeB prepares the handover regarding layer 1 and layer 2 and sends a
HANDOVER REQUEST ACKNOWLEDGE message via X2 to the source eNodeB. The HANDOVER REQUEST ACKNOWLEDGE message includes a transparent container to be sent to the UE later as part of the CONNECTION RECONFIGURATION message. The container includes the new C-RNTI and the value of the dedicated preamble to be used by the UE to synchronise with the target cell as well as other parameters required by the UE.
6. The SN STATUS TRANSFER message is sent from the source to the target eNodeB.
Thereby PDCP layer information is transferred to ensure uplink and downlink PDCP SN continuity for every bearer that requires PDCP status preservation.
7. Some time after sending the CONNECTION RECONFIGURATION message to the UE (and
possibly before sending the SN STATUS TRANSFER message to the target eNodeB), the source eNodeB begins forwarding user data in the form of PDCP SDUs using the resources set up previously and continues as long as packets are received at the source eNB from the EPC.
9. The random access response conveys timing alignment information and initial uplink grant
for handover.
10. When the UE has successfully accessed the target cell, it sends the CONNECTION
RECONFIGURATION COMPLETE message (containing its new C-RNTI) to the target eNodeB to indicate that the handover procedure is completed for the UE.
TTA LTE/MIMO Standards/Technology Training 31 Nokia Siemens Networks
12. The target eNodeB sends a PATH SWITCH REQUEST message to the MME to inform it
that the UE has been handed over to another eNodeB.
13. The MME sends a USER PLANE UPDATE REQUEST message to the S-GW, which
includes the target eNodeB's TEID(s) received before to enable the user data path to be switched from the source to the target eNodeB.
14. The S-GW switches the downlink data path to the target eNodeB.
Before the S-GW can release any U-plane/TNL resources towards the source eNodeB, it sends one or more end marker packet(s) to the source eNodeB as an indication that the downlink data path has been switched.
15. The S-GW sends a USER PLANE UPDATE RESPONSE message to the MME to confirm
that it has switched the downlink data path.
16. The MME confirms the PATH SWITCH REQUEST message with the PATH SWITCH
REQUEST ACK message.
17. By sending a UE CONTEXT RELEASE message, the target eNodeB informs the source
eNodeB of the success of the handover and triggers the release of resources. The target eNodeB does not release its data forwarding tunnels from the source eNodeB until it has received an end marker packet.
18. Upon reception of the UE CONTEXT RELEASE message, the source eNodeB may forward
any remaining PDCP SDUs
TTA LTE/MIMO Standards/Technology Training 32 Nokia Siemens Networks
RRC Timers
Timer Start T300 Transmission of RRCConnectionRequest T301 Transmission of RRCConnectionReestabilshmentRequest Reception of RRCConnectionReject while performing RRC connection establishment Access barred while performing RRC connection establishment for mobile originating calls Reception of RRCConnectionReconfiguration message including the MobilityControl Info or reception of MobilityFromEUTRACommand message including CellChangeOrder Access barred while performing RRC connection establishment for mobile originating signalling Access barred while performing RRC connection establishment for mobile originating CS fallback. Upon detecting physical layer problems i.e. upon receiving N310 consecutive out-of-sync indications from lower layers Upon initiating the RRC connection reestablishment procedure Upon receiving t320 or upon cell (re)selection to E-UTRA from another RAT with validity time configured for dedicated priorities (in which case the remaining validity time is applied). Upon receiving measConfig including a reportConfig with the purpose set to reportCGI Upon receiving LoggedMeasurementConfiguration message Stop Reception of RRCConnectionSetup or RRCConnectionReject message, cell re-selection and upon abortion of connection establishment by upper layers Reception of RRCConnectionReestablishment or RRCConnectionReestablishmentReject message as well as when the selected cell becomes unsuitable Upon entering RRC_CONNECTED and upon cell re-selection Upon entering RRC_CONNECTED and upon cell re-selection At expiry Perform the actions as specified in 5.3.3.6 Go to RRC_IDLE
T302 T303
Inform upper layers about barring alleviation as specified in 5.3.3.7 Inform upper layers about barring alleviation as specified in 5.3.3.7 In case of cell change order from E-UTRA or intra EUTRA handover, initiate the RRC connection reestablishment procedure; In case of handover to EUTRA, perform the actions defined in the specifications applicable for the source RAT. Inform upper layers about barring alleviation as specified in 5.3.3.7 Inform upper layers about barring alleviation as specified in 5.3.3.7
T304
Criterion for successful completion of handover to EUTRA or cell change order is met (the criterion is specified in the target RAT in case of inter-RAT)
T305
T306
T310
T311
Upon receiving N311 consecutive in-sync indications from lower If security is not activated: go to RRC_IDLE else: layers, upon triggering the handover procedure and upon initiate the connection re-establishment procedure initiating the connection re-establishment procedure Selection of a suitable E-UTRA cell or a cell using another RAT. Enter RRC_IDLE
T320
Upon entering RRC_CONNECTED, when PLMN selection is performed on request by NAS, or upon cell (re)selection to another RAT (in which case the timer is carried on to the other RAT).
Upon acquiring the rmation needed to set all fields of cellGlobalId for the requested cell, upon receiving measConfig that includes removal of the reportConfig with the purpose set to reportCGI Upon log volume exceeding the suitable UE memory, upon initiating the release of LoggedMeasurementConfiguration procedure
T321
Initiate the measurement reporting procedure, stop performing the related measurements and remove the corresponding measId Perform the actions specified in 5.6.6.4
T330
Constant Usage TTA LTE/MIMO Standards/Technology Training N310 Maximum number of consecutive "out-of-sync" indications received from lower layers 33 Nokia Siemens Networks N311 Maximum number of consecutive "in-sync" indications received from lower layers
* Harri Holma and Antti Toskala, LTE for UMTS: OFDMA and SC-FDMA Based Radio Access, Wiley, 2009
TTA LTE/MIMO Standards/Technology Training 35 Nokia Siemens Networks
+40%
MIMO
Inter-cell interference rejection combining Total
+15%
+10% =3.0x
* Harri Holma and Antti Toskala, LTE for UMTS: OFDMA and SC-FDMA Based Radio Access, Wiley, 2009
TTA LTE/MIMO Standards/Technology Training 36 Nokia Siemens Networks
2G CDMA 3G WCDMA 4G LTE 4G LTE planned (2nd carrier) Empty spectrum To be assigned (12-13)
900MHz B8
KT UL (10) 9 1 5 9 5 0 KT DL (10) 9 6 0
1.8GHz B3
frequency sharing b/w comm & military/public (35) 1 7 1 0 1 7 4 5
KT UL (10)
1 7 5 5
SKT UL (10 )
1 7 6 5 1 7 7 0
LG U+ UL (10)
1 7 8 0
KT DL (10) 1 8 5 0
SKT DL (10 ) 1 8 6 0
LG U+ DL (10) 1 8 7 0
2.1GHz B1
LG U+ UL (10 )
1 9 2 0 1 9 3 0
SKT UL (30)
1 9 6 0
KT UL (20)
1 9 8 0
IMT-satellite (30) 2 0 1 0
LG U+ UL (10 )
2 1 1 0 2 1 2 0
SKT UL (30)
2 1 5 0
KT UL (20)
2 1 7 0
IMT-satellite (30) 2 2 0 0
Multi-Carrier Operation
Mobility
Intra-frequency handover Inter-frequency handover
Load balancing
Idle mode cell selection priority Idle mode load balancing
1st carrier
TTA LTE/MIMO Standards/Technology Training 38 Nokia Siemens Networks
MC CA
MC (Multi Carrier)
: SKT 850MHz 2x10MHz 1.8GHz 2x10MHz MC LTE 850MHz 2 850MHz 1.8GHz , 850MHz 1.8GHz , PDR 2 DL 75Mbps
CA (Carrier Aggregation)
N . SKT PDR 2 DL 150Mbps MC Intra-band contiguous CA () Intra-band non-contiguous CA Inter-band (non-contiguous) CA ()
* CA Band Combination
Typical AMR-NB payload of 14 32 bytes (4.75 kbit/s 12.2 kbit/s) Leads to > 50% reduction of data volume at the air interface
Proper level of LTE network performance itself PDCCH, PDSCH, PUSCH capacity Coverage performance, particularly in cell edge RAN optimization (parameter/field optimization) becomes more
critical in VoLTE era
Establishment time
Default bearer Established when UE connects to PDN Provides always-on connectivity Always non-GBR Dedicated bearer established later Can be GBR or non-GBR
Allocation and retention priority (ARP): This determines whether a bearer can be
dropped if the network gets congested, or whether it can cause other bearers to be dropped. Emergency calls might be associated with a high ARP, for example.
TTA LTE/MIMO Standards/Technology Training 47 Nokia Siemens Networks
CSI table
0 0 3 1 1 1 0 3 2 1 1 1 2 1 0 3 0 0
Channel aware
UE A UE B UE C
Resulting weight: 12
Channel unaware
Resulting weight: 2
SRVCC to WCDMA
VoIP continuity to WCDMA
Extension to WCDMA handover Only applied if EPS bearer with
QCI = 1 is established and MME indicates that SRVCC is possible
S-GW MME MSC
RNC
Hurdles to overcome
Call drop shall be minimized
GSMA IR.92 says If the PDN connectivity is lost, then the UE must re-establish the PDN
connection.
Connection RLF Re-establishment Fail? Call drop Network optimization is THE key.
3.00 2.50 2.00 bps/Hz 1.50 1.00 0.50 0.00 0% 13% 25% 38% 51% Loading 63% 76% 88%
3GPP Case 1 simulations with full buffer gives 1.74 bps/Hz/cell
Assumes nice hexagonal grid + uncorrelated antennas
8000
6000 4000 2000 0 0 50 100
150
200
250
300
350
400
Thank you !
www.nokiasiemensnetworks.com Nokia Siemens Networks 20F, Meritz Tower, 825-2 Yeoksam-Dong, Kangnam-Gu Seoul 135-080, Korea