01_04_RA41151EN162GLA0_LTE16_RRM.pdf

Nokia Academy RA4140 FL16 Feature Delta Radio Resource Management and Telecom Features LTE Features

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

Copyright and confidentiality The contents of this document are proprietary and confidential property of Nokia Solutions and Networks. This document is provided subject to confidentiality obligations of the applicable agreement(s). This document is intended for use of Nokia Solutions and Networks customers and collaborators only for the purpose for which this document is submitted by Nokia Solutions and Networks. No part of this document may be reproduced or made available to the public or to any third party in any form or means without the prior written permission of Nokia Solutions and Networks. This document is to be used by properly trained professional personnel. Any use of the contents in this document is limited strictly to the use(s) specifically created in the applicable agreement(s) under which the document is submitted. The user of this document may voluntarily provide suggestions, comments or other feedback to Nokia Solutions and Networks in respect of the contents of this document ("Feedback"). Such Feedback may be used in Nokia Solutions and Networks products and related

2

specifications or other documentation. Accordingly, if the user of this document gives Nokia Solutions and Networks feedback on the contents of this document, Nokia Solutions and Networks may freely use, disclose, reproduce, license, distribute and otherwise commercialize the feedback in any Nokia Solutions and Networks product, technology, service, specification or other documentation. Nokia Solutions and Networks operates a policy of ongoing development. Nokia Solutions and Networks reserves the right to make changes and improvements to any of the products and/or services described in this document or withdraw this document at any time without prior notice. The contents of this document are provided "as is". Except as required by applicable law, no warranties of any kind, either express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose, are made in relation to the accuracy, reliability or contents of this document. NOKIA SOLUTIONS AND NETWORKS SHALL NOT BE

RA41151EN162GLA0

RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT or for any loss of data or income or any special, incidental, consequential, indirect or direct damages howsoever caused, that might arise from the use of this document or any contents of this document. This document and the product(s) it describes are protected by copyright according to the applicable laws. Nokia is a registered trademark of Nokia Corporation. Other product and company names mentioned herein may be trademarks or trade names of their respective owners. © Nokia Solutions and Networks 2016

© Nokia Solutions and Networks 2016

This page contains no comments

Contents • • • • • • • • • • • • • • • • •

4

LTE44: 64QAM in UL LTE439: SGW Relocation with X2 Connection LTE915: S1 eNodeB Configuration Update LTE1059: Uplink Multi-cluster Scheduling LTE1068: S1/X2 Satellite Connection LTE1536: RRC Connection Rejection with Deprioritization LTE1541: Advanced SCell Measurement Handling LTE1569: QCI1 Specific RLF and Re-establishment Control LTE1638: Inter-frequency RSTD Measurement Support LTE1709: Liquid Cell LTE1819: Data Session Profiling LTE1891: eNodeB Power Saving – Micro-DTX LTE1987: Downlink Adaptive Close Loop SU MIMO (4x4) LTE2007: Inter-eNodeB Carrier Aggregation LTE2026: RRC Signaling Robustness - Downlink LTE2098: VoLTE Uplink Coverage Boosting LTE2115: Dual Transmission Mode 1 Operation

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

Contents • • • • • • • • • • • • • • • • • • 5

LTE2162: SRVCC for Network Deployments Not Supporting PS HO LTE2166: Support of Dedicated Idle Mode Mobility Priorities LTE2167: Additional Carrier Aggregation Band Combinations 3CC - I LTE2180: FDD-TDD Downlink Carrier Aggregation 2CC LTE2200: Additional Carrier Aggregation Band Combinations – III LTE2205: Configurable Uplink Interference Regions LTE2206: Extended RLF Handling LTE2210: Intra-frequency Load Balancing Extensions LTE2233: N-out-of-M Downlink Carrier Aggregation LTE2275: PCell Swap LTE2316: FDD-TDD Downlink Carrier Aggregation 3CC LTE2351: S1-based Handover towards CSG Cells LTE2390: MME Selection-based upon Only MMEC and PLMN ID LTE2465: CSG Cell Support LTE2470: Centralized RAN CL16 Release LTE2503: Emergency Call-based Mobility Trigger LTE2505: Access Class Barring Skip LTE2598: ARP-based QoS Profiling RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE44: 64QAM in UL Before and after LTE44 • Feature LTE44 introduces 64 QAM modulation scheme in UL increasing maximum achevable UE uplink throughput in a very good radio conditions and improving average cell capacity • Higher peak UL throughputs can be achieved due to the support of higher Modulation and Coding Schemes (MCSs)  MCS 21 – MCS 28

UL CELL Capacity

UL CELL Capacity

Without LTE44 – 64QAM in UL

6

RA41151EN162GLA0

With activated LTE44 – 64QAM in UL

© Nokia Solutions and Networks 2016

This page contains no comments

LTE44: 64QAM in UL • Feature LTE44 introduces 64 QAM modulation scheme in uplink extending the range of Modulation and Coding Schemes (MCSs) that can be used by the UL Adaptive Modulation and Coding (AMC) mechanism • 64 QAM modulation scheme characteristics: -

Supported in uplink by the MCS 21 – MCS 28

-

Carries 6 bits per single modulated symbol (3 times more than QPSK and 1.5 time more than 16 QAM)

-

RESTRICTION: supported only by the 3GPP Category 5 and Category 8 UEs

7

QPSK

I

I

I 11

Q

Q

Q

1111

RA41151EN162GLA0

16 QAM

111111

© Nokia Solutions and Networks 2016

64 QAM

This page contains no comments

LTE439: SGW Relocation with X2 Connection S-GW relocation during X2 handover overview •

X2-based handover with Serving GW relocation is defined in 3GPP 23.401

•

The above-mechanism should be used if there is no connection between eNBs and all of the Serving Gateways -

•

8

MME

eNB receives information about E-RABs which should be switched and E-RABs which should be released If necessary, eNB sends message to UE about Data Radio Bearer(s) to be released

X2

Target eNB

Source eNB

The mechanism may be also triggered due to load balancing in Evolved Packet Core (EPC)

RA41151EN162GLA0

Target S-GW

Source S-GW

MME may decide to move U-Plane traffic during ongoing X2 handover to another Serving Gateway (S-GW) •

•

P-GW

© Nokia Solutions and Networks 2016

U-Plane C-Plane

This page contains no comments

LTE439: SGW Relocation with X2 Connection Before & after LTE439 feature

Before

After

• Relocation of Serving Gateway triggered during completion phase of X2 based handover led to connection release

• Flexi Multiradio BTS supports the change of Serving Gateway during X2 based handover

9

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE439: SGW Relocation with X2 Connection Technical Details

- Switching of E-UTRAN Radio Access Bearers (ERABs) in uplink direction in case signaled Transport Layer Address indicates another S-GW than so far used by source eNB •

List with E-RAB ID, Transport Layer Adresses and GTP-TEID

- E-RAB releasing due to MME decision List contains E-RAB(s) ID which need to be released and cause of releasing

10

RA41151EN162GLA0

Source

E-Rab To Be Switched in Uplink List

MME

> E-RABs Switched in Uplink Item IEs

MME

>> E-RAB ID

MME

>> Transport Layer Address

MME

>> GTP-TEID

MME

E-RAB To Be Released List

MME

> E-RAB List Item

MME

>> E-RAB ID

MME

>> Cause

MME …

•

Information Element Name …

• LTE439 feature introduces 2 new mechanisms – triggered by S1AP: Path Switch Request Acknowledge

© Nokia Solutions and Networks 2016

This page contains no comments

LTE915: S1 eNodeB Configuration Update Purpose of the S1 eNode B Configuration Update procedure • Before LTE16 release update of configuration data i.e. eNB Name (LNBTS:enbName), Tracking Area Code (LNCEL:tac) and Further PLMN Ids (LNCEL:furtherPlmnIdL) requires restart of eNB or reset of S1 link

eNB

MME

New configuration eNB restart

S1 Setup Request

- With LTE915 it is possible to update abovementioned parameters without restart of the eNB and without reset of the S1 link

S1 Setup Response

• Before LTE16 MME is informed by eNB of Paging DRX Cycle equal to 2560ms. Value sets on eNB cells is not taken into account at all. - Change of LNCEL:defPagCyc does not lead to trigger of S1 Setup Request - With LTE915 MME is always updated with the highest configured value of all eNB’s cells

MME

eNB New configuration

eNB Configuration Update eNB Configuration Update Acknowledge

11

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE915: S1 eNodeB Configuration Update Purpose of the S1 eNode B Configuration Update procedure • S1 eNode B Configuration Update procedure is triggered by the eNB to interoperate properly via S1 interface with MME • Feature LTE915 does not have a feature activation flag and it is always activated in FL16/TL16 releases

eNB

MME

New configuration eNB restart

S1 Setup Request S1 Setup Response

MME

eNB New configuration

eNB Configuration Update eNB Configuration Update Acknowledge

12

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE915: S1 eNodeB Configuration Update Before & after

Before eNB Name

Paging DRX

Tracking Area Code

Further PLMN Ids

Restart of eNB

yes

no

yes

no

Reset of S1 link

yes

no

yes

yes

result

13

MME uses always the maximum value of Restart of eNB Restart of eNB Paging DRX Cycle Re-establishment of leading also to S1 link leading also to S1 link (2560ms) S1 link reset reset independently of the value set on cells of eNB

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE915: S1 eNodeB Configuration Update Before & after

After eNB Name

Paging DRX

Tracking Area Code

Further PLMN Ids

eNB restart

no

no

no

no

S1 reset

no

no

no

no

result

Data updated without impact on eNB and S1 link

MME gets always the highest configured value of all eNB’s cells

Data updated without impact on eNB and S1 link

Data updated without impact on eNB and S1 link*

(*) S1 partial reset will be triggered for all the UE S1 connection with the obsolete PLMN ID.

14

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE915: S1 eNodeB Configuration Update S1 eNode B configuration update - Successful Operation

eNB New configuration

1

3

15

The Operator changes configuration data e.g. eNB Name

2

eNB sends eNB Configuration Update message to the MME with updated informations

3

eNB waits up to 60 seconds for response from MME with acknowledge message

4

MME responds with eNB Configuration Update Acknowledge message before 60 seconds are expired

eNB Configuration Update

2

4

1 MME

x

eNB Configuration Update Acknowledge

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE915: S1 eNodeB Configuration Update S1 eNode B configuration update - Unsuccessful Operation (1/2) • Unsuccessful eNB Configuration Update procedure may happen when: eNB

MME

New configuration eNB Configuration Update

eNB Configuration Update

x

eNB Configuration Update Failure eNB Configuration Update

- eNB does not receive response from MME within 60 seconds upon sending eNB Configuration Update - eNB receives from MME eNB Configuration Update Failure message before 60 seconds expires

• Three consecutive unsuccessful eNB Configuration Update attempts detected by eNB leads to the failure of the whole S1 eNB Configuration Update procedure - S1 configuration update fault ( eNB

16

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

) is raised by the

This page contains no comments

LTE915: S1 eNodeB Configuration Update S1 eNode B configuration update - Unsuccessful Operation (2/2)

eNB

MME

New configuration eNB Configuration Update

•

If S1 eNB configuration update can not be performed and fault is raised, following scenarios are possible: -

eNB Configuration Update

x

unsuccessful, S1 setup will be triggered. It leads to the re-establishment of the

eNB Configuration Update Failure eNB Configuration Update

If TAC, Further PLMN Ids update were

respective S1 link -

S1 setup will not be triggered if update of the eNB Name or the Default Paging DRX failed

17

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE1059: Uplink Multi-cluster Scheduling Before LTE1059 LTE944 PUSCH masking •

It allows to exclude certain uplink resources from being used, therefore no transmission will take place in certain sections of the uplink band (PRBs are blanked) PUSCH area 1

18

•

It allows using blanked PRBs from one side of spectrum for PUSCH scheduling, in scenario when LTE786 Flexible uplink bandwidth is in use

PUSCH area 2

Blanked PUSCH

• •

LTE825 Outer region scheduling

PUSCH area 1

PUCCH

Blanked PUSCH

PUSCH area 2

PUCCH

Both of the functionalities cause that PUSCH is fragmented into 2 areas As uplink resource allocations have to be continuous. As a result PUSCH division is causing peak UE throughput to decrease as single UE has to be scheduled in only one of PUSCH areas

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE1059: Uplink Multi-cluster Scheduling Motivation for LTE1059 • In case when LTE944 PUSCH masking or LTE825 Outer region scheduling is used in the network, PUSCH spectrum is divided into several PUSCH areas • Divided PUSCH causes uplink peak UE throughput decrease when only one UE is scheduled in single TTI, because UE can be scheduled only in one PUSCH area at the time • LTE1059 Multi-cluster scheduling introduces possibility to schedule UE in two PUSCH areas at the same time when there is only one UE scheduled in single TTI Before: Single UE can be scheduled in only one PUSCH area in single TTI

PUCCH PUSCH area 1

PUSCH area 2

PUCCH

After: Single UE can be scheduled in two PUSCH areas in single TTI. Peak throughput is increased

19

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE1059: Uplink Multi-cluster Scheduling Conditions for LTE1059 usage • Multi-cluster scheduling can be applied for a UE only when following conditions are met: - PUSCH is divided into 2 or more areas - There is only one UE in time domain scheduling set (only one UE is requesting for transmission in given TTI) - UE supports multi-cluster scheduling - UE has enough power so that BLER target can be fulfilled - Amount of data in the buffer and selected MCS indicate that UE needs more PRBs that are available in PUSCH area in which it would be placed - Supported system bandwidths are:

20

•

5MHz,10MHz, 15MHz or 20MHz when LTE825 Outer region scheduling is used

•

10MHz, 15MHz, 20MHz when LTE944 PUSCH masking is used

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE1068: S1/X2 Satellite Connection • •

•

The LTE1068: S1/X2 Satellite Connection feature allows a satellite connection within E-UTRAN (between two eNBs) and between E-UTRAN and a core network. The feature provides a basic data and voice service for an eNB when a terrestrial connection is not available. The LTE1068: S1/X2 Satellite Connection feature supports a low bandwidth slower speed eNB backhaul with high round trip time. This enables the basic set of existing features to continue to work. A backhaul is used to get data to a point from which it can be distributed over a network. An eNB backhaul may also connect to other eNBs via a satellite link. In such cases, the delay is doubled if both eNBs have satellite links at their ends, connecting them to routers in the core network. This could be the case for an X2 interface or an S1 handover, where both: source and target eNBs have a satellite backhaul (SBH). Based on the following performance factors:

Factor Packet Delay

Value 490 ms max (one-way)

Comment The maximum Packet Delay means that 99.9% of packets are faster than this.

Packet Jitter

100 ms max (one-way)

The maximum Packet Jitter means an absolute value (not +/-). Jitter is typically asymmetric. Using +/- 50 ms around the maximum Packet Delay would not be correct even though in absolute terms that would be 100 ms. The jitter variation results in overall Packet Delay varying between 390 ms and 490 ms, one-way.

Packet Loss Rate

Handover Trigger Change := new deltaCio

• Small cell n accepts CIO adjustment:

105

-

Small cell n sends MCA (Mobility Change Accept) message,

-

eICIC manager updates the LNREL parameter cellIndOffNeighDelta for small cell n and starts timer TCioModProhibit.

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE2210: Intra-frequency Load Balancing Extensions UE capability and QCI of bearers • UE measurement reconfiguration depends on UE capability, QCI of bearers, and if applyFeIcicFunctionality is enabled. CIO setting is based on following if applyFeIcicFunctionality = TRUE: new cellIndOffNeighDelta 6dB

mlbE icicOperMode

mlbE icicOperMode

mlbE icicOperMode

mlbE icicOperMode

= ‘allUE s’

!= ‘allUE s’

= ‘allUE s’

!= ‘allUE s’

(cellIndOffNeigh + new cellIndOffNeighDelta ) for all UE s

(cellIndOffNeigh + new cellIndOffNeighDelta )

(cellIndOffNeigh + new (cellIndOffNeigh + new cellIndOffNeighDelta ) for cellIndOffNeighDelta ) for all R11 UE s w/o GBR all R11 UE s w/o GBR bearers bearers

(cellIndOffNeigh + max. (cellIndOffNeigh + max. 6dB) for all R8/9/10 UE s 6dB) for all UE s with w/o GBR bearers, see GBR bearers and all also Note 1 R8/9/10 UE s w/o GBR cellIndOffNeigh for all cellIndOffNeigh for all bearers, see also Note 1 UE s with GBR bearer(s) UE s with GBR bearer(s)

• If applyFeIcicFunctionality = FALSE then cellIndOffNeighDelta must be csgId, or UEs performing manual CSG selection will try to access this cell

Note: For non-3GPP compliant UE and MME it is possible non-CSG UE can connect CSG cell

126

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE2470: Centralized RAN CL16 Release • •

•

•

127

The LTE2470: Centralized RAN CL16 Release feature is based on the FDD-LTE 16 release, and supports Centralized RAN (CRAN) deployment for 1Rx and 2Rx cells with 5, 10, 15, and 20 MHz bandwidth. Centralized RAN improves uplink (UL) inter-cell interference handling for dense cell deployments by extending the Co-ordinated Multipoint (CoMP) set size. In a dense radio deployment, it is difficult to manage interference. The UEs' antennas radiate 360o causing interference in neighboring cells. This feature improves an aggregate uplink throughput in an interference-limited environment. The LTE2470: Centralized RAN for CL16 Release feature guarantees: -

the UL service during mass events (seamless gains in UL for nomadic users across the CRAN system)

-

improved throughput with up to 30% less UE power consumption

-

on average up to 200% UL capacity gains for 2Rx per cell (MIMO, SIMO) deployment

-

up to 170% gains for 1Rx per cell (SISO) deployment

-

It also eliminates cell's edge performance degradation.

-

The LTE2470: Centralized RAN for FL16 feature ensures support of FBBC, which is more widely used at the customer side.

The CRAN solution is an extension of the intra eNB CoMP functionality. The CoMP set consists of cells from one or two interconnected eNBs. The eNBs exchange UL I/Q data from cells that belong to a particular CoMP set. The eNBs operate as independent entities. Each eNB supports up to four cells. This feature allows the operator to connect up to nine eNBs and obtain ten CoMP set combinations. For the LTE2470: Centralized RAN CL16 Release feature, the CRAN CoMP set size for CRAN is six or five (in case of three cells per FSMF). It means that five or six cells (including the serving cell) are considered by the eNB to process UL I/Q data. The eNB with the serving cell uses the IRC algorithm to combine the Physical Uplink Shared Channel (PUSCH) signals in such a way that the overall post-equalizer signal to interference and noise ratio is maximized. All other physical UL signals are received based on the serving cell's antennas.

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE2503: Emergency Call-based Mobility Trigger •

The LTE2503: Emergency Call-based Mobility Trigger feature introduces an enhancement for the traffic-steering schemes that are based on quality class indicator 1 (QCI 1). The feature's functionality is related to the specific UEs with QCI1: those with VoLTE emergency calls, or with emergency calls that do not support reference signal time difference (RSTD) capability.

LTE2503 benefits •

The LTE2503: Emergency Call-based Mobility Trigger feature provides the following benefits: -

possibility to increase the accuracy of location services based on the observed time difference of arrival (OTDOA) during VoLTE emergency calls.

-

possibility to steer all UEs with VoLTE emergency calls to the preferred and configurable LTE frequency layers.

LTE2503 functional description •

The LTE2503: Emergency Call-based Mobility Trigger feature is an enhancement of the LTE1127: Service-based Mobility Trigger feature.

•

The LTE1127: Service Based Mobility Trigger feature introduces a mechanism for service-triggered inter-frequency handover. Within its scope it is possible to configure specific VoLTE services target frequency layers within mobility profiles.

•

Moreover, the operator can deploy and configure its network with LTE1127: Service Based Mobility Trigger so that some specific frequency layers are preferred over other layers for VoLTE calls and eNB will try to steer UE with VoLTE calls to those preferred layers with Service Based Handover. For other LTE frequencies and QCI 1 bearers, see Figure: Different LTE frequencies and QCI 1 bearers.

•

The LTE2503: Emergency Call-based Mobility Trigger feature introduces an additional filter criterion based on an allocation and retention priority (ARP). It also enhances traffic-steering schemes based on QCI 1 that can be limited to emergency calls and dependency of a UE capability for RSTD functionality. The location accuracy for OTDOA in combination with an emergency call for all UEs that do not support an inter-frequency RSTD measurement is improved. The handover (HO) triggered by this feature is more reliable than the one from the LTE1127: Service-based Mobility Trigger feature since it has no negative impact on the drop rate of emergency calls.

128

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE2505: Access Class Barring Skip • The LTE2505: Access Class Barring skip feature supports an ability to apply the Access Class Barring only for chosen services. The services that will not be barred automatically can be specified using special parameter transmitted in System Information Block 2. The following services can be skipped when using the LTE2505: Access Class Barring skip feature: - MMTEL-Voice, when using the ac-BarringSkipForMMTELVoice LNCELparameter - MMTEL-video, when using the ac-BarringSkipForMMTELVide LNCELparameter - SMS service, when using the ac-BarringSkipForSMS LNCEL-parameter

•

The feature can be used in combination with the LTE1788: Access Class Barring feature. • The feature improves a system behavior in overload scenarios. It helps to utilize an available bandwidth and capacity in more effective way.

129

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE2598: ARP-based QoS Profiling ARP based QoS profiling • LTE2598 ARP based QoS profiling feature introduce scaling of non-GBR QoS parameters based on ARP • Operator is able to boost/deboost experience for certain ARP • Feature can be used to improve experience for new specific UE models introduced to the network (without UE knowledge) • Non-GBR QoS parameters scaled: - scheduling weight (schedulWeight) - nominal bitrate (nbrDl / nbrUl)

130

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE2598: ARP-based QoS Profiling Before & after

Before

After

• No possibility for QoS based on ARP

• Possibility to boost/deboost experience for certain ARP

• ARP values not affecting scheduling principles • Differentiation possible only based on QCI

• Possibility to differentiate parameters nbrUl, nbrDl and schedulWeight parameters inside same QCI based on ARP • ARP values may affect scheduling • Another level of flexibility for scheduling management

131

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments

LTE2598: ARP-based QoS Profiling Before & after

Before

After DRB #1 (QCI5, ARP=1)

DRB #1 (QCI5, ARP=1) DRB #3 QCI6

ARP=6 nbrUL / nbrDl schedulWeight

UE1

DRB #3 QCI6

ARP=6 nbrUL / nbrDl schedulWeight

UE1

Same QCIs

eN B

eN B UE2

UE2

Example: Feature enabled for ARP=7 (arpPrioLev =7) Result: Two bearers with same QCI are differentiated by means of nbrDL , nbrUl and schedulingWeight by scaling factors nbrUlDlSF and schedulingWeightSF 132

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

Scaling parameters

This page contains no comments

RA41151EN162GLA0

© Nokia Solutions and Networks 2016

This page contains no comments