Circle Teams Discussion

Samsung NEO
5 Sep 2018
Content
A
s
Package 7.5.0. Ph1
Narrow Band IoT
4 CRS
Timing Advance Type 1
ALDM & DwPTS Blanking
Frequency Priority Handover
EPC Upgrade & Features
NFV and Virtual EPC

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 2

Package 7.5.0 Phase 1 - Enhancements

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 3
Summary – Enhancements 1/2
No Title Description Status
The Cell Number range The Cell Number range is increased from 0~26 to 0~53,
1 recognized by the user has allows to plan and configure New Additional Sectors (in Tested Successfully in LAB
increased. 850/1800 band 4th, 5th & 6th Sectors)

Msg3 and Msg5 enabling

parameter It allows handling sleeping cells by auto DSP INIT & Cell Tested Successfully in LAB/Field.
2 (ZERO_CALL_CONFIG) to be Reconfiguration, based on criteria defined in Network GUI CLI command now available
configurable via GUI/CLI to change parameter values

Previously alarm was Service affecting alarm.

From PKG750:
1. CPRI PORT Mismatch alarm is not NSA alarm.
3 CPRI Port Mismatch alarm 2. Additional info of alarm provides reason of alarm is Tested successfully in LAB & Field
due to "Branch ID" or "Serial Number" mismatch
3. From PKG750, RTD01A RU doesn’t generate RRH
communication fail alarm in such a case.

Previously, only ports of 9&10&11 of LCC2 board and

RTD01A were supported optic bitrate mismatch alarm
4 Optic Bitrate Mismatch From PKG750: Tested successfully in LAB & Field
Alarm 1. Supported RU type and port are expanded to all RUs
and port of LCC2.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 4

Summary – Enhancements 1/2
No Title Description Status
From PKG750:
Frequency Bandwidth 1. This feature support Bandwidth change without cell deletion Tested successfully in LAB for
5 Change (1800 & 850 Band) or eNB reset. both 1800 and 850 band
2. Only support from 5 M to 10 M bandwidth change of 1.8GHz
or 850MHz band is available on SLR750V2 PKG.

Previously, SYS FAN FAIL (NSA) alarm with Major severity was
raised FAN Communication fail and FAN HW Fail.
From PKG750: Tested successfully in LAB.
6 Communication Fail Alarm 1. SYS FAN Alarm is now split into two alarm, No any alarm observed in
with Ancillary Devices a. FAN Communication Fail (Minor alarm) and Field for FOA sites.
b. FAN Fail (Major alarm).
2. It allows to distinguish between communication issue or HW
issue.

Previously, If only 850 2nd carrier growth and no cells created

in 1st carrier then 850Mhz cell setup fail issue was observed.
7 System Reset and Restart From PKG750: Tested in Lab Successfully
(LCB3 cell setup fail) 1. DSP Image selection criteria is changed, hence if only 2nd
carrier growth done in 850Mhz then DSP image can be
processed and Cell Setup successful

Previously, Some optic module has no wavelength reading

Inventory Management - function. So, garbage data is showing at LSM. Enhancement working is
8 Enhancement From PKG750, RX wavelength for such Optic module which is observed in FOA sites
beyond normal range will be displayed as “-”
2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 5
System Creation and Deletion - Enhancement
The Cell_ID range is increased from PKG750v2-Ph1 Current CNUM-IDs are In-Use
Software release
• In PKG710, supported Cell ID

• From PKG750, supported Cell ID

CDU and RDU both supports extended Cell_ID

• Currently 24 CNUMs are In-Use in network and only
3 CNUMs (21, 22, & 24) are available.
• Extended Cell IDs, enable to integrate new band and
sectors in Jio Network (e.g: 1.8G & 850 band additional
Additional sector in Testing
Bi-sectors i.e. 4th 5th & 6th sector)

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 6

Msg3 and Msg5 enabling parameter configurable
In PKG710 this parameter was PLD parameter but was not configurable by CLI com-
mand in GUI.
From PKG750, Msg2 & Msg5 enabling parameter “ZERO_CALL_CONFIG” is now con-
figurable from LSMR GUI command CHG/RTRV-ENB-INF.
This is enhancement is to set the DSP Reset behavior by Configuration of
“ZERO_CALL_CONFIG” parameter.
DSP Configuration specific settings of this parameter are as follows
• 0 : DSP_INIT ON (alarm OFF) & CELL_RECF ON
• 1 : DSP_INIT OFF & CELL_RECF ON
• 2 : DSP_INIT ON (alarm OFF) & CELL_RECF OFF
• 3 : DSP_INIT OFF & CELL_RECF OFF
• 4 : DSP_INIT ON (alarm ON) & CELL_RECF ON
• 5 : DSP_INIT ON (alarm ON) & CELL_RECF OFF
• DSP_INIT - Reset DSP if RRCConnectionSetupComplete is not received for 30 minutes.
• CELL_RECF - CELL Reconfiguration if RRCConnectionRequest is not received for 30 minutes.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 7

CPRI Port Mismatch alarm – Enhancement 1/2
In PKG710, if RRH CPRI Port Mismatch alarm triggered, then RRH communication fail
alarm was occurred causing RRH TX OFF.
From PKG750,
1. Tx off should not be executed when CPRI connection mismatch alarm is raised.
• Tested in LAB successfully, FA = ON even if CPRI_PORT_MISMATCH alarm reported.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 8

CPRI Port Mismatch alarm – Enhancement 2/2
2. Additional information is now reported, when CPRI port mismatch alarm is raised, due to
“branch ID” or “serial number” mismatch detection.
• Tested in LAB with CPRI swap between two Sectors – Alarm Reported with additional info “[SERIAL
NUM MISMATCH]”
• Tested in LAB with CPRI swap between L0/L1 ports of single RRH – Alarm Reported with additional
info “[PORT ID MISMATCH]”

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 9

Optic Bitrate Mismatch Alarm - Enhancement
In PKG710, only ports of 9&10&11 of LCC2 board and RRH RTD01A were supported
Optic Bitrate Mismatch alarm
From PKG750, This alarm is supported by all RU type and all ports of LCC2 Board of RDU

• Limitations:- RRH-T5 cannot support the 10Gbps SFP, because the RRH FPGA can support only
below 6Gbps speed. So, if configure PLD of RRH-T5 as 10Gbps, CPRI Fail alarm can be occurred.
2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 10
Bandwidth Change – Enhancement – 1/1
In PKG710, to change frequency bandwidth, cell deletion was required
In PKG750;
• This feature allows to change frequency bandwidth without cell deletion or eNB reset
• Only support from 5 M to 10 M bandwidth change of 1.8GHz or 850MHz band is available in
SLR750V2 PKG.

There are some limitations that need to be considered when using this function
• Bandwidth change is only possible in the Administrative state locked
• UL CoMP feature and Carrier-Aggregation feature, must be OFF when changing Bandwidth.
• For LCC, all cells in the same DSP must be in the Administrative state locked
• If one RRH supports two carriers(ex. 850M 2 Carrier), the Bandwidth change function will not
be supported
• Administrative state of Smart Scheduler should be locked ahead of bandwidth change and
then change it to unlock after bandwidth change
• After bandwidth change, inband NB-IoT‟s DL/UL RB position is changed to default value

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 11

Bandwidth Change – Enhancement – 2/2
Cell Parameter window (CONFIGURATION Cell Parameter)

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 12

Communication Fail Alarm with Ancillary Devices
In PKG710, SYS FAN FAIL (NSA alarm) has “MAJOR” severity and has two main com-
ponents i.e. FAN FC and FAN MD
• When communication between UMP and FAN module is disabled then this alarm is raised.
• Due to MAJOR severity, alarm need attention for clearance, even the alarm is non service
affecting alarm.
In PKG750, separate alarm for FAN Communication Fail and FAN Module Fail with dif-
ferent severity.
• FAN Communication Fail (UMP and FAN Module link is disturbed) with MINOR Severity.

• FAN MD (FAN Module Hardware Alarm) with MAJOR Severity

Limitation:
• If the Slave FAN (FAN[1]) be removed from the slot in RDU, only the
“FAN_COMMUNICATION_FAIL” alarm will occur because of HW limitation.
• But if Master FAN (FAN[0]) be removed from the slot in RDU, the
FAN_COMMUNICATION_FAIL and FAN_FAIL will occur.
2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 13
System Reset and Restart (LCB3 cell setup fail) (1/2)
After upgrade eNB to SLR710, 850MHz cell setup fail issue was occurred.
• In the problem site, 3cells (dspLogicalCellNum : 3, 4, 5) were created in second carrier and
there was no cell created in first carrier. DSP image can process only when first carrier
(dspLogicalCellNum 0,1,2) is also created.
From PKG750, the criterion for selection DSP image is changed.
• Whether cell is created in second carrier, DSP image selection criterion is changed.
• If 3cells (dspLogicalCellNum: 3, 4, 5) are created in second carrier, DSP image that can
process dspLogicalCellNum 0~5 is loaded.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 14

System Reset and Restart (LCB3 cell setup fail) (2/2)
Tested in Lab, 850 band only 2nd carrier growth done and cells setup done normally.

No 1st Carrier
2nd Carrier grown

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 15

Inventory Management - Enhancement
Enhancement in Inventory management for display of RX wavelength of SFP modules
(RTRV-SFP-INVT)
• Normal range of Rx wavelength is 850nm ~ 1620nm.
• Some optic module has no wavelength reading function. So, garbage data is showing at LSM.

From PKG750, RX wavelength for such Optic module which is beyond normal range
will be displayed as “-”.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 16

NB-IoT.

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 17
3GPP NB-IoT

Cat M1
(Rel.13 eMTC)
Cat 0
Cat 1 (Rel.12)
(Rel.8)

• Reducing Peak rate (1Mbps) • Repeated Trasmission

• Reducing Peak rate (10Mbps)
• Single Rx receiver (1T1R) • Narrow bandwidth (1.4MHz)
• Half duplex mode • Extended DRX
• Power saving mode • CP optimization, UP optimization

Support Various
Improved Improved
Low bit-rate Ap-
Coverage Battery life Deployment
plication
• Guard-band
+ 21dB expansion > 10 years Channel BW : 200kHz • In-band
than LTE Transmission BW: 180kHz • Stand-alone

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 18/19

3GPP Re.13 Cellular IoT – Narrow Band IoT

NB-IoT supports three operating mode

• Support Cat-NB1 device
• NB-IoT carriers (200KHz) are deployed with/without the LTE carrier
• Power Spectrum Density Boosting, Repetition
- Max. 21 dB Coverage extension expected
• Flexible deployment options
- Guard-band, In-band, Standalone

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 19/19

NB-IoT Operation Mode: Guard-band Mode

There is no LTE RB resource reservation

NB-IoT carrier shall be within the guard-band of LTE carrier and satisfy the require-
ment of Out-of-Band emission

LTE Channel BW = 10 MHz BW

NB-IoT Data
NB-IoT RS
NB-IoT Transmission BW = 180 kHz

LTE Transmission BW = 9 MHz

NB-IoT
subcarrier

...
NB-IoT symbol
Guard-band mode

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 20/31

NB-IoT Operation Mode: In-band Mode

LTE DL/UL 1RB resources are reserved

In-band mode throughput is less than guard-band mode throughput because

NB-IoT cannot use the area of LTE’s PDCCH and CRS

LTE Channel BW = 10 MHz BW

NB-IoT Data LTE PDCCH
LTE Transmission BW = 9 MHz NB-IoT RS LTE CRS
NB-IoT Transmission BW = 180 kHz

NB-IoT
subcarrier

...
NB-IoT symbol
In-band mode

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 21

NB-IoT Operation Mode: Stand-alone Mode

NB-IoT carrier is located in a new frequency, Re-farming one or more GSM or

other-RAT channels

Resource usage of NB-IoT stand-alone mode is similar to NB-IoT guard-band mode

LTE Channel BW = 10 MHz BW NB-IoT Transmission BW NB-IoT Data

NB-IoT Transmission
= BW = NB-IoT RS
200 kHz
180kHz

LTE Transmission BW = 9 MHz

NB-IoT
subcarrier

...
Stand-alone mode NB-IoT symbol

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 22/31

NB-IoT Coverage Enhancement Level

Max. 3 Coverage Enhancement Levels are defined per RSSI sensitivity level

Coverage Enhancement Levels are supported by PHY repetition

— DL: Max. 2048
— UL: Max. 128

Cat.NB1 sends the signal with max. Tx Power within enhance coverage

Coverage Enhancement example

• CE Level 0: 144dB
Normal coverage • CE Level 1: 154dB
• CE Level 2: 164dB
Enhanced coverage

CE Level 0
CE Level 1
NB-IoT Coverage
CE Level 2

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 23/36

Comparison NB-IoT Guard-band vs In-band

NB-IoT guard-band operation mode has less impact to LTE performance than
NB-IoT in-band mode
Performance Guard-Band In-Band
LTE DL User Peak Throughput Loss Reference 4.2%▼
LTE
(10MHz) LTE UL User Peak Throughput Loss Reference 11.4%▼

NB-IoT NB-IoT Capacity Loss Reference 28%▼

Guard band NB-IoT In-band NB-IoT

NB-IoT Data
Reserved for LTE such as
※ Channel BW 10MHz NB-IoT CRS LTE PDCCH, LTE CRS
© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 24/36
NB-IoT Single Device Peak
PHY Peak data rate (1)
It only takes NPDSCH transmission time for TBS 680 bits into account.
(Guard-band)227kbps = 680bits/3ms, (In-band)
• DL: 227 kbps(Guard-band), 170 kbps(In-band)
(1)
170kbps=680bits/4ms
(2)
It only takes NPUSCH transmission time for TBS 1000 bits into account.
• UL: 250 kbps
(2)
250kbps = 1000bits/4ms

Effective Peak data rate of Single Device (3)

TBS= 680bit, scheduling delay for half duplex
27.2kbps = 680bits/25ms (Guard-band)
• DL: 27.2 kbps(3)
(4)
TBS= 1000bit, scheduling delay for half duplex
62.6kbps = 1000bits/16ms
• UL: 62.5 kbps(4)
1ms 3ms 2ms

A A
N N N N C C
N
P Scheduling P P P Scheduling K K Scheduling P
Downlink D delay (4ms) D D D delay (12ms) / / delay (3ms) D
Peak Data Rate C S S S N
A
N
A
C
C C C C C
C C
H H H H K K H

NPDSCH Transmission time = 25ms

1ms 4ms

N N N N N N
P Scheduling P P P P Scheduling P DL channel
Uplink D delay (8ms)
U U U U delay (3ms) D
Peak Data Rate C S S S S C
C C C C C C UL channel
H H H H H H

NPUSCH Transmission time = 16ms

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 25/36

NB-IoT Architecture
New Interface
- S11-U* : newly defined for user data forwarding between MME and S-GW
- T6a* : newly defined for Non-IP user data forwarding, device connection management between MME and SCEF
Enhanced Interface
- Uu (Rel.13) : RRC messages, IEs and procedures are added for NB-IoT
- S1-MME (Rel.13) : NAS message format, IEs are added for user data transportation by using CP optimization

Legacy LTE EPC Core

Legacy LTE Interface
NB-IoT Interface MME
S1-U
(CP Optimization)
S11 SGi IP Network
S5
S-GW P-GW
S1-MME
LTE Uu
Device
Macro eNB S1-U
w/ NB-IoT CIoT Core (C-SGN) SGd
SMSC
NB-IoT
Device Uu (Rel.13) S1-MME
SMS
(Rel.13) T6a*

LSM MME Non-IP Data SCEF*

S11
SCEF : Service Capability Exposure Function S11-U*
SGi
SCS : Service Capability Server S5
S-GW P-GW IP Data SCS/AS
SMSC : Short Message Service Center
* : new interface or new NE © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 26/30
NB-IoT Guard-band Frequency (LTE 10MHz)
NB-IoT Guard-band Default Frequency (Left: Default)
 E.g. Mumbai
 B5 [DL: 877.995MHz ~ 887.835MHz (9.84MHz), UL: 832.995MHz ~ 842.835MHz (9.84MHz)]
832.995 842.835 877.995 887.835
(UL) LTE 9.84MHz BW (DL) LTE 9.84MHz BW
NB-IoT 180kHz NB-IoT 180kHz
BW LTE Transmit BW=9MHz BW
Foffset>225kHz@10 LTE Transmit BW=9MHz
M

837.9 MHz 882.9 MHz

405 kHz Guard band 435 kHz Guard band 405 kHz Guard band 435 kHz Guard band

833.31 MHz 878.3025 MHz

<=> EARFCN (100 kHz unit) + UL CH. Raster offset (-50~45 kHz, <=> EARFCN (100 kHz unit) + Anchor DL CH. Raster offset (±2.5 kHz
5 kHz unit) or ±7.5 kHz)

[3GPP TS 36.101 Rel.13] Foffset for category NB1 UE spectrum emission mask

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 27/31

NB-IoT Guard-band Frequency (LTE 5MHz*)
NB-IoT Guard-band Default Frequency (Left: Default)
 E.g. Punjab
 B3 [DL: 1825.1MHz ~ 1830.3MHz (5.2MHz), UL: 1730.1MHz ~ 1735.3MHz (5.2MHz)]
1730.1 1735.3 1825.1 1830.3
(UL) LTE 5.2MHz BW (DL) LTE 5.2MHz BW
NB-IoT 180kHz NB-IoT 180kHz
BW LTE Transmit BW=4.5MHz BW
Foffset>200kHz@5 LTE Transmit BW=4.5MHz
M

1732.8 MHz 1827.8 MHz

(100kHz right (100kHz right
450 kHz Guard band shift) 450 kHz Guard band shift)
250 kHz Guard band 250 kHz Guard band

1730.4 MHz 1825.4075 MHz

<=> EARFCN (100 kHz unit) + UL CH. Raster offset (-50~45 kHz, <=> EARFCN (100 kHz unit) + Anchor DL CH. Raster offset (±2.5 kHz
5 kHz unit) or ±7.5 kHz)

[3GPP TS 36.101 Rel.13] Foffset for category NB1 UE spectrum emission mask

* NB-IoT Guard-band mode in 5MHz is available where the occupied bandwidth is larger than equal to 5.15MHz
© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 28/31
NB-IoT PCI Allocation
LSM automatically allocates PCI of NB-IoT cell based on location information and/or paired LTE cell information
For automatic allocation for NB-IoT PCI, positioning information of NB-IoT cell should be input, or automatic
position information update function should be turned on.

PCI of NB-IoT cell is allocated/changed as follows

NB-IoT mode PCI allocation mode At creating a new NB-IoT cell In Operation
Initial PCI = OFF PCI should be manually configured

Initial PCI = ON PCI is automatically allocated by SON algo- PCI does not change auto-
Guard-band rithm* matically
Use Parent PCI = ON PCI used by paired LTE is automatically allo-
cated
Initial PCI = OFF PCI should be manually configured
In-band PCI changes
(DifferentPCI) PCI used by paired LTE is automatically allo- automatically**
Initial PCI = ON
cated

* The algorithm is same with the algorithm for normal LTE cell. Brief algorithm is as follows.
1) PLI (Physical Layer Identity) is selected by considering “CellNum and PLI mapping rule”.
2) A PCI with selected PLI is randomly allocated among the PCIs which are not used by the cell within predefined distance
** When PCI of the paired LTE cell changes by PCI AutoConfiguration feature, PCI of NB-IoT cell is automatically reallocated
to the same value as the PCI of paired LTE cell. This operation is due to the following limitation defined in specification.
- If the mode of NB-IoT cell is inband-DifferentPCI mode, “PCI % 6” of the NB-IoT cell and paired LTE cell should be same.
© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
NB-IoT Transmission Power
RU power is shared by LTE and NB-IoT

“nrsPowerBoosting” parameter is supported for NB-IoT Transmission power setting

— nrsPowerBoosting is the power ratio between NB-IoT NRS power and LTE CRS power
— The range of nrsPowerBoosting is -6dB ~ 11dB (default: 9dB)

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 30/30

NB-IoT Cell Management (1/2)
Cell Creation and deletion
 Cell creation and deletion of NB-IoT cell is supported separately with LTE cell.

Configuration Management
 NB-IoT cell number is the same as the cell number of LTE.
 Configuration Data (PLD)/CLI command for NB-IoT are added.
 Transmit power configuration of NB-IoT cell

LSM Client LSM

HTTP

Operator
SNMP/FTP

LTE Only eNB

LTE+NB-IoT eNB

Single Management Interface

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 31/19

NB-IoT Cell Management (2/2)
State Management
 Administrative State (Locked, Unlocked, Shutting Down) for NB-IoT cell
• Administrative State of the NB-IoT cell can be configured separately with LTE cell.
• Shutting Down Timer option is supported. (Forced HO option is not supported.)
• Administrative state of system controls the administrative states of both LTE cell and NB-IoT cell.
• When the administrative state of NB-IoT cell is locked, I/Q data of NB-IoT cell is blocked.
• When both the NB-IoT cell and the parent LTE cell are locked, the transmit power of the carrier
which is mapped to them in RU is off.

Fault Management
 DIGITAL_OUTPUT_HIGH/DIGITAL_OUTPUT_LOW alarm for NB-IoT cell is defined.
 SERVICE_OFF alarm for NB-IoT cell is defined to indicate that all NB-IoT cells in a eNB are out of
service.

Test Management
 N-TM (NB-IoT Test Model) is provide for RF property test of NB-IoT cell.

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 32/19

4CRS

2016 © Samsung Electronics. All Rights Reserved.©Confidential

Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 33
About 4CRS (1/2)
4CRS(4x2 MIMO)
• Multiple antenna techniques aim to improve data robustness or provide an increase in
data rates by utilizing special signal structure and exploiting un-correlated fading channels
for each transmitted signal. In case of four transmit antennas on an eNB and two receive
antennas on the same UE, it is known downlink 4x2 single-user MIMO. The following figure
shows the concept of single user MIMO using m transmit and n receive antennas.

• As shown in the figure above, each receiver side antenna receives a composite signal
made up of transmitted signals modified by their channels. Under specific channel
conditions, the transmitter can structure the transmitted signals to, either send modi-
fied copies of the same transmission (transmit diversity) or, send different transmis-
sion (spatial multiplexing). The former case provides signal robustness and the latter
provides increase in data rate.

2018 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 34

4CRS – Pros & Cons
Benefit
• DL throughput enhancement
• Exploiting beamforming gain due to more accurate precoding
# of CRS Number of precoding matrix
2 4
4 16

• IP throughput gain in Patna

4CRS Patch
KPI Band 2CRS VoLTE fallback + VoLTE TBS deci- Delta
(23, 24-Aug) sion
(28-Aug)
2300 Band (20
MHz) 1.99 2.46 23.71%
IP Throughput [Mbps]
2300 Band (10
MHz) 2.07 2.36 14.02%

2018 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 35

4CRS – Pros & Cons
Limitation
1) Available # of REs per RB reduces as 5% due to the increase of CRS overhead

R0 R0
One antenna port

R0 R0

R0 R0

R0 R0
l 0 l 6 l 0 l 6

Resource element (k,l)

R0 R0 R1 R1

2CRS
Two antenna ports

R0 R0 R1 R1
Not used for transmission on this antenna port

R0 R0 R1 R1
Reference symbols on this antenna port

R0 R0 R1 R1
l 0 l 6 l 0 l 6 l 0 l 6 l 0 l 6

R0 R0 R1 R1 R2 R3
Four antenna ports

R0 R0 R1 R1 R2 R3
4CRS
R0 R0 R1 R1 R2 R3

R0 R0 R1 R1 R2 R3
l 0 l 6 l 0 l 6 l 0 l 6 l 0 l 6 l 0 l 6 l 0 l 6 l 0 l 6 l 0 l 6

even-numbered slots odd-numbered slots even-numbered slots odd-numbered slots even-numbered slots odd-numbered slots even-numbered slots odd-numbered slots

Antenna port 0 Antenna port 1 Antenna port 2 Antenna port 3

2018 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 36

About 4CRS (2/2)
Advantage

• More closed-loop gain

• The set of 4x2 precoder is larger than 2x2 precoder.  More precoder selection gain

[Disadvantage]

• More cell-specific RS (CRS) overhead

• The number of data REs decreases due to additional 2nd and 3rd CRS overhead
• Worse channel estimation performance
• The CRS density of 2nd / 3rd CRS port is the half of that of 0th / 1st CRS port.
• The channel estimation performance of 4x2 is worse than that of 2x2.

2018 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 37

2CRS vs 4CRS (2/2)
2CRS vs 4CRS
• View of DL Scheduler
2CRS 4CRS DL scheduler Comment

Considering increased CRS overhead, RB/ In condition of 2x2 UE, Error Free Condition,
CRS overhead 9.5% 14.3%
MCS is determined ideal DL Peak throughput can be decreased

Port (0, 1): Port (0, 1):

8 8 In case of 4CRS, because the number of port 2 &
No. RE for CRS 3 is smaller than that of port 0 & 1, the perfor-
per RB Port (2, 3): Port (2, 3):
mance of channel estimation of UE can be de-
graded
0 4

TDD Special Sub-

For TDD Special subframe, MCS should be For SSF 2-6, MCS is reduced as much as 1.
frame, Max. coding 0.930 0.908
limited to not over Max. coding rate For SSF 2-7, MCS is not changed
rate Limitation

• View of PDCCH
• Same algorithm for CCE aggregation level is applied
• Even if the size of TM Specific DCI Format payload for 4CRS is 3bit more large, there is no impact to
performance
• The size of payload for DCI 0 & 1A format is same

2018 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 38

Virtual Matrix for Tx Power Equalization in 4CRS (1/2)
CRS Position and Tx. Pwr Imbalance in 4CRS (w/o Virtual Matrix)
• Power Imbalance between antenna ports happens because Antenna 2 and 3 have half of
RE for CRS.

Ant0 Ant1 Ant2 Ant3 Total

Sym0 13.3 13.3 6.7 6.7 40.0
Sym1 6.7 6.7 13.3 13.3 40.0
Sym2 10.0 10.0 10.0 10.0 40.0
Sym3 10.0 10.0 10.0 10.0 40.0
Sym4 13.3 13.3 6.7 6.7 40.0
Sym5 10.0 10.0 10.0 10.0 40.0
Sym6 10.0 10.0 10.0 10.0 40.0
Sym7 13.3 13.3 6.7 6.7 40.0
Sym8 6.7 6.7 13.3 13.3 40.0
Sym9 10.0 10.0 10.0 10.0 40.0
Sym10 10.0 10.0 10.0 10.0 40.0
Sym11 13.3 13.3 6.7 6.7 40.0
Sym12 10.0 10.0 10.0 10.0 40.0
Sym13 10.0 10.0 10.0 10.0 40.0

2018 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 39

Solution to resolve Coverage Issue
Issue : After coverage gets reduce by 3 dB of 4CRS enable eNB,
• Resulting cell edge UE shift to lower band

Solution 1 : Change Multi carrier Setting

• Currently UE move from TDD to FDD at -113 dBm
• Instead of this UE will shift at -116 dBm
• Some other multicarrier changes are required to support 3dB variation

Solution 2: Apply 6dB boosting at CRS

• For Cell reference signal add 6dB instead of 3 dB
• Advantage :
• RSRP measurement will remain same no changes require in multicarrier setting
• Disadvantage :
• PDSCH power will get reduce

2018 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 40

4CRS enhancement

2018 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 41

DCI 1 A for VoLTE

2018 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 42

DCI 1 A for VoLTE

2018 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 43

DCI 1 A for VoLTE

2018 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 44

TM4 TX Diversity for Data

2018 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 45

TA Type 1 Testing

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.

2016 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 46
Test Scenario
Test Plan
• Stationary UE at Pre-Defined location from EnodeB.
• UE Behavior
• UL FTP
• VoLTE.
• Capturing UE TA from True Call for the test time..
• Comparing the True call TA distance with actual UE location.

Defined Distance

2016 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 47

TA type 1 Working
Big TA : Timing Off set Estimated using PRACH preamble [TA]
Small TA [MAC CE] : periodic in every 1sec [TA]
• If with measurement window TA >= 1TA then 1 else 0
Ta type 1 : to the true call server in every 10 sec [min 2Ts]

EXAMPLE
Current Position Initial Attach

UE Moves away from eNB

TS (2Ts) 3 2 1 7 6 5 4 3 2 1 7 6 5 4 3 2 1 7 6 5 4 3 2 1

TA 5 4 3 eNB RX-TX
Small TA/ MAC CE BIG TA difference

Example case
• Current UE Location (TA) : 86Ts
• Big TA = 3 TA (initial UE Location)
• Small TA : Big TA + Small TA + eNB Rx – Tx Time difference /16 (TA) = 5TA
• TA Type1 : Big TA*8 + Small TA*8 + eNB Rx –Tx Time difference/2 (2Ts) = 43Ts
• True call distance = ((TA Type 1)+0.5)*9.78 mtrs = (43+0.5)*9.78 = 425 mtrs

2016 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 48

Test Results
FTP Test results
Distance +/- 1 TA samples at 75 Mtrs +/- 1 TA samples at 154 Mtrs +/- 1 TA samples at 230 Mtrs
CP LYF CP LYF CP LYF
2300 C1 88 % 82% 47% 63% 75% 89%
2300 C2 55 % - 71% 20% 16% 57%
1800 71 % 68% 18% 32% 45% 40%
850 96% 93% 65% 82% 62% 68%

VoLTE Test Results

Distance +/- 1 TA samples at 75 Mtrs +/- 1 TA samples at 154 Mtrs +/- 1 TA samples at 230 Mtrs
CP LYF CP LYF CP LYF
2300 C1 95 % 97% 95% 87% 100% 97%
2300 C2 100 % 100% 46% - 20% 100%
1800 96 % 98% 95% 78% 95% 71%
850 96% 93% 89% 83% 98% 88%

• FTP Test Results are not conclusive , VoLTE test shows better accuracy compare to FTP test

2016 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 49

Further Action
Further analysis

• Need to analysis deviation in actual distance & True call value

• Need to analysis different TA value for Volte and UL FTP

• Need to analysis different behavior of different handset

Further Test

• Different location from eNB

• NLOS condition

• Different RRH type eNB

2016 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 50

ALDM and DwPTS Blanking

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 51
Interference Issue in TDD (due to Propagation Delay)
Propagated DL signal of Cell-A is interfering UL frame in Cell-B
Illustration of Interference Issue in Circle Boundary
1. Any DL Signal falling in UL window creates
high Uplink RSSI
Over reaching Down Circle Boundary
Link signals from one 2. Mitigation is very Difficult in areas of high
eNode B to another Cell-A terrain difference
creates strong 3. Mitigation through coverage confinement
interference in uplink
> 40km possible in same AMSL areas
(in TDD) .

Also these signals are

Cell-B
not restricted by
Earth’s Curvature and
travel large distances
1 millisecond = 300 kms
214 .3 kms
42.8 kms 10 + 2 + 2 symbols in Special
Sub frame Configuration 7
Cell-A Tx DwPTS (10) GP(2) UpPTS (2)

Cell-A Propagation Delay when it reaches B DwPTS GP UpPTS

Cell-B Tx DwPTS GP UpPTS DL of Cell A Interfering to UL

time of Cell B
Propagation Delay Symbols Distance in km
DwPTS (End) to UpPTS (Beginning) 2 42.86 CP will slightly add to
DwPTS (Beginning) to UpPTS (End) 14 300.00 distance
© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
ToF interference
Time-of-flight (ToF) interference:
• Affects TDD systems only
• Aggressor cell’s DL transmission affects victim cell’s UL transmission (UpPTS symbols and UL subframes)
• Interference occurs when
• Radio line-of-sight between aggressor and victim cells
• Insufficient antenna down-tilt or terrain height difference or atmospheric conditions leading to ducting
• Aggressor and victim cells are separated by a distance larger than guard period (GP) propagation distance of special
subframes (SSFs)
• Effect: UL & DL throughput is lowered TDD configuration-2
D S U D D D S U D D
DL transmission
power Dw- GP UpPTS
PTS
DwPTS GP UpPTS
SSF – 3 9 2
5
14 symbols
SSF – 10 2 2
7

time
GP UpPTS + UL SF

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 53

Special Sub-frame Configuration Changes
 Mitigation:
14 10 2 2 14
 With the present SSF configuration of “7”
Config-7

DL DwPTS GP UpPTS UL signals can sustain a propagation delay up to

~43Km, and after certain distance the DL
symbols in SS is interfering the Uplink time
14 10 2 2 14
period affecting frame orthogonally
DL DwPTS GP UpPTS UL  We Can Change Special Subframe Configura-
tion from 7 to 5, which will increase Gap pe-
14 3 9 2 14
riod in SS and Signals can sustain delay up to
Config-5

DL DwPTS GP UpPTS UL 193 Km.

 DL throughput can reduce by 20% when SS
changed from 7 to 5
14 3 9 2 14 SS 5 recommended as interferers are at
DL DwPTS GP UpPTS UL distance > 130 kms

Special Subframe DL/UL TDD Configuration Table Throughput Comparison

Configuration Table No. of SF Per
Subframe number
DL to 10ms frame
Symbols / subframe Config Expected DL
Config Gap In Index UL UL/DL Special
Index KMs (mS) 0 1 2 3 4 5 6 7 8 9 D U S Throughput % Change in Peak
Dw GP Up [DL] [UL] [SSF] TDD Subframe
(With MIMO DL Throughput
Config. Config.
0 3 10 1 214.3 2*2) in Mbps
1 9 4 1 85.7
0 5 D S U U U D S U U U 2 6 2

2 10 3 1 64.3 1 5 D S U U D D S U U D 4 4 2
2 7 112 NA
3 11 2 1 42.9 2 5 D S U D D D S U D D 6 2 2
4 12 1 1 21.4
5 3 9 2 192.86
3 10 D S U U U D D D D D 6 3 1
2 5 97 -20 %
6 9 3 2 64.3 4 10 D S U U D D D D D D 7 2 1
7 10 2 2 42.86 5 10 D S U D D D D D D D 8 1 1
8 11 1 2 21.4
6 5 D S U U© Samsung
U Electronics.
D S AllURightsUReserved.
D Confidential
3 and 5 Proprietary.
2
SS Change – Throughput Loss of 20%
Lab Test carried out for TDD Configuration 2-7 In 2-5 Configuration , the DwPTS cannot
•
be used for downlink scheduling
Data Call Tests Successful
 DL throughput reduced by 20%. This is expected behavior
For DL in TDD Config 2-7, 14 Symbols X 6 Sub-frame + 10 Symbols of SS X 2 = 104 Symbols
For DL in TDD Config 2-5, 14 Symbols X 6 Sub-frame + 0 Symbols of SS = 84 Symbols

As per 3GPP36.213 7.1.7 – “The UE may skip decoding a transport block in an initial transmission if the effective channel code rate is
higher than 0.930, where the effective channel code rate is defined as the number of downlink information bits (including CRC bits) divided by the
number of physical channel bits on PDSCH. If the UE skips decoding, the physical layer indicates to higher layer that the transport block is not suc -

cessfully decoded. For the special subframe configurations 0 and 5 with normal downlink CP or configurations 0 and 4 with ex-

tended downlink CP, shown in table 4.2-1 [3], there shall be no PDSCH transmission in DwPTS of the special sub frame ”

• Intra-eNB handover Successful in Lab

• VoLTE Tests Successful in Lab
• SS Change then implemented in HP on 6 Nov 2015 and in PJ on 9 Nov 2015

Reduction of DL Symbols from 104 to 84 in 10 ms frame when SS changed

from 7 to 5 (around 20% loss in peak throughput )
© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
ToF interference mitigation - ALDM
LTE-OM9018 Automatic Long-distance Interference Detection and Mitigation (TDD)
• Concept:
• SSF-5 uses less DwPTS symbols than SSF-7
• Change the SSF configuration of aggressor cells to SSF-5 to reduce interference
• Operation:
• Interference measurement preparation:
• Cell barred, forced HO to other cells, SSF configuration changed to SSF-7
• Interference measurement:
• Cell barred, forced HO to other cells, DL OCNS transmission
• RSSI measurement on UpPTS symbols and 1st seven UL subframe symbols
• SSF configuration update:
• If interference > threshold, SSF configuration changed to SSF-5
• Configuration of victim is changed due to LoS reciprocity
• Requires cell barring, forced HO, and SIB-1 update
• Issues:
• ALDM works on a time-scale of hours  not fast enough
• Cell outage (due to lock / unlock) and high signaling load (due to HO)
• Interference detection up to ~230 km only
• Not performed independently on 2 carriers with same RRH
• DL Throughput Loss in day time when there is no ToF Interference

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 56

ToF interference mitigation
ALDM interference measurement + DwPTS blanking:
• Concept: If SSF configuration change is required, blank the DwPTS instead of changing SSF configuration
• Operation:
• Interference measurement preparation, interference measurement, and SSF configuration change condition check:
• Operator should be able to perform these operations independently and simultaneously on both cells of the
same RRH
• Preparation & measurement methods and SSF configuration change condition are same as in current ALDM
solution
• DwPTS blanking:
• If SSF configuration change condition and time-period condition are satisfied, start DwPTS blanking
• Time-period condition: Operator can configure a time-period (e.g., 10:00 am to 01:00 pm) in which
blanking should be used
• Interference measurement is done at night-time while blanking is required during day-time 
time-period for blanking is needed
• Victim cell is blanked due to LoS reciprocity
• 1st DwPTS symbol and CRS REs will not be blanked
• If HARQ re-transmission is needed, DwPTS may be scheduled while blanking is on-going
• Interference mitigation range is similar to current ALDM solution (~230 km)
• Blanking stop condition: Operator-configured time-period has expired
• Blanking should start automatically each day until:
• Operator turns-off blanking feature, or
• New ALDM interference measurement is performed which shows that blanking is no longer needed

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.

ToF interference mitigation
ALDM interference measurement + DwPTS blanking:
• Advantages over ALDM:
• Can be started / stopped over a configured time-period  lower DL throughput loss
• Cell barring and forced HO not needed
• Can be performed independently on 2 carriers with same RRH
• New parameters:
• BlankingUseFlag (per cell):
• 1: DwPTS blanking is used
• 0: SSF configuration change is used
• BlankingStartTime (per cell): Start time of time-period in which blanking can be used
• BlankingStopTime (per cell): Stop time of time-period in which blanking can be used
• Start & stop times should be configurable with a granularity of 15 minutes (00:00, 00:15, …, 23:30, 23:45)

BlankingUseFla BlankingUseFla Comments

g for C1 g for C2

0 0 Both C1 & C2 can use SSF configuration change

independently
C1 and C2 are 20MHz and
0 1 C1 can use SSF configuration change 10MHz carriers, respectively,
C2 can use DwPTS blanking of the same RRH

1 0 C1 can use DwPTS blanking

C2 can use SSF configuration change
1 1 Both C1 & C2 can use DwPTS blanking independently
© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.
ToF interference mitigation
Automatic DwPTS Blanking for Interference Mitigation (ADBIM):
• LTE-OM9018 (ALDM) feature:

Manually-triggered Per-symbol UL
interference measurement RSSI counters
ADBIM

SSF configuration change DwPTS blanking

LTE-OM9018

Before SLR7.5 JIO: In SLR7.5 JIO:

• Manually-triggered • Manually-triggered interference measurement
interference measurement or per-symbol UL RSSI counters
• SSF configuration change • SSF configuration change or DwPTS blanking

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.

ToF interference mitigation
Automatic DwPTS Blanking for Interference Mitigation (ADBIM):

Measurement Measurement Qtr. = Quarter =

duration duration Qtr. 15 minutes

time
...
- ALDM switch = Start time Stop time
Blanking duration Blanking duration
ADBIM
- ADBIM parameter ADBIM window
setting

• Operation:
• ALDM switch = ADBIM and ADBIM parameter settings • Per-cell UL RSSI counters
• ADBIM window start and stop times are configurable • RssiSymbol0Avg (MACB)
• Measurement duration: Based on per-symbol UL RSSI, decide • RssiSymbol0Tot (PM block)
• RssiSymbol0Cnt (PM block)
to blank DwPTS in blanking period or not
• …
• Blanking duration: If needed, blank DwPTS • RssiSymbol12Avg (MACB)
• For the last period, measurement / blanking stops if ADBIM • RssiSymbol12Tot (PM block)
window is over before measurement / blanking period • RssiSymbol12Cnt (PM block)
• ADBIM window will automatically repeat every 24 hours
RSSI of symbol-13 is excluded
since it cannot be measured
accurately by S8400.

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.

FPHO Functionality Test

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.

2016 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 61
FP-HO Feature
Lower band can be offloaded to Higher Band by FPHO
• Normal coverage based inter-frequency handover will not be triggered as long as coverage condition is not
met in serving/target cell
• In the multicarrier environment like JIO, different handover schemes regardless of serving cell coverage is
required, based on operators policy for particular band utilization.
• FPHO is a forced handover based on pre-assigned frequency priority. Where users will be handover to high
priority band , if coverage condition and Load condition is satisfied in target high priority carrier.

Handover from 1800 to 2300

will occur when RSRP and
1800 Capacity condition is met for
2300 M 2300 band, regardless of
M
1800 RSRP

Handover Handover Pros Cons

Type Criteria

Lesser signaling, due to less • Uneven usage of carriers

Service Based Serving and/or • • Handover Ping Pong between MLB and
Handover Target cell RSRP number of RRC service based handover
Reconfigurations TDD-FDD CA will not work effectively
•

Frequency • Can prioritize particular

Priority based Target Cell RSRP carrier for loading
Handover and Load • Handover ping pong will be • RRC Signaling will be increased
(FPHO) reduced
• TDD-FDD CA work effectively
2016 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 62
FPHO Functionality (2/2)
Why We need FPHO in our network?
For effective use of MLB-
• With normal service based handover, we have to keep MLB A4 threshold too high, to avoid ping pong
between MLB and service based handover.
• With FPHO, we can relax MLB A4 threshold as low as possible, because FPHO will not allow users to
handover if target cell is loaded than threshold. This will give very good MLB gain as well as reduced ping
pong handovers.
For effective use of TDD-FDD CA-
• With normal service based handover, if user in enjoying TDD-FDD CA and handover criteria from FDD to TDD
is satisfied, user will move to TDD where CA will not work.
• With FPHO, when user is enjoying TDD-FDD CA, it will come back to TDD as FPHO will not allow UE to
handover to 2300 band. This will enhance effective use of Carrier Aggregation.

FPHO Key Parameters-

Band Priority- We can keep higher priority for band which have more capacity. E.g. 20 M,10 M
A4 Threshold- RSRP Criteria for handover to target Cell
CAPA Threshold- Available Capacity threshold for target threshold

2016 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 63

Summary
Test Area- Mumbai Cluster 108/109
Test Objective- To check FPHO functionality in PKG750

Below is Overall Summary

SSSR and CC346 are showing same trend after A1 based FPHO. So ASR issue resolved in PKG750

IP Throughput improved by 11% after FPHO Implementation.

CA DL Volume and CA Addition time shows good Improvement. CA Efficiency has increased.

High loaded 850 band offloaded to less loaded 2300-C2 after FPHO implementation

FPHO has not impacted SSSR, ERAB Setup, CRR346, which were degraded earlier in PKG600P3

IP Throughput improved in 2300-C1 and 850 band. SSSR , Volte Drop rate improved in 850 band.

MCR Shows fluctuation before and after FPHO implementation.

Many other KPIs are altered due to traffic distribution change after FPHO

2016 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 64

EPC Core Network – Journey So far

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.

2016 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 65
Capacity installed and utilized – (As of 30th Aug)

GW Installed Capacity
4 Weeks
0 368 Nos.
Mn . in 1
178
22 Tbps
Utilized Capacity
16 Tbps

MME
Installed Capacity
112 (2214 LESA)
633 Mn
Utilized Capacity
177 Mn

2016 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 66

EPC Package

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 67
EPC PKG Release update

15 Feb. 15 May. 15 Aug 29 Aug

8.0.0 8.0.0
NFV (vGW) (vMME) 8.0.0

Features
Common (Virtual and Legacy)
DSCP in TFT Filter Support
TAC based barring in SAEGW

Legacy 5.2.0 Inter PLMN Handover allowable

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 68

EPC PKG 8.0.0 – Key Features
Description
Separate inactivity timer

Allow Inter PLMN Handover Calls

Increasing number of whitelist TAC from 5000 to 10000 (IMEI TAC based IPv6 Only Allocation)

TAC based barring in SAEGW

Support of Charging Behavior to select Virtual APN

Supporting TOS feature in TFT with Predefined PCC rules

Include Last Cell id in Offline CDR

LMA feature for enterprise service with support for AAA Authentication ON/OFF
SAEGW assigning S11 interface IP in Modify bearer response instead of S1U IP
(Session Handling during S1U LAG failures)
Inline Software Upgrade Phase 1

Enhancement for creation of new Bearer by detecting Destination IP

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 69

Separate inactivity timer
Description
• For a dedicated bearer, when RAR sent by PCRF to remove the PCC rule do not reach the
SAE-GW, then SAE GW keeps that stale bearer for a longer duration until the user makes an
explicit detach and re-attach .
• This also affects the CDR duration which remains open till the time bearer exists.
• To remove all such stale default and dedicated bearers, following four inactivity timers are
introduced.
• Inactivity timer for active default bearer
• Inactivity timer for active dedicated bearer
• Inactivity timer for idle default bearer
• Inactivity timer for idle dedicated bearer
• If there is no traffic flow for a particular bearer till specified time in Inactivity timer, SAEGW
perform corresponding action
• NONE – SAEGW does not do anything
• DETECT – SAEGW generate Status and Summary messages.
• DISCONN – SAEGW delete this bearer (default and dedicated).

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 70

Allow Inter PLMN Handover Calls
Description
• PLNM is used to define each circle boundary.
• Whenever there is a PLMN change, UE is reattached unconditionally.
• In case of Vo-LTE service the call is dropped, this impacts the customer experience.
• To overcome this issue and improve the customer experience and VoLTE KPI, following
corrections are implemented.
• After receiving HO/TAU message, MME will check for PLMN change PLMN and mark it
in MM context
• If there is QCI-1 (VoLTE) bearer, MME will send HO / TAU reject.
• If there is no QCI-1 (VoLTE) bearer, MME will process the HO / TAU request and wait for Delete
Bearer Request for QCI1.
• After receiving the Delete Bearer Request, MME will detach the UE with reattach required.
• Save the counters for this actions
• With this implementation, in case of Handover or Tracking Area Update (TAU) with PLMN
change, the existing call will continue across the circle boundary, detach and reattach will
happen at the end of the call.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 71

Whitelist TAC count increase (5000 to 10000)
Description
• IMEI TAC whitelisting is being used as of now for IMS APN.
• This helps to reduce the IPv4 consumption as if the device support IPv6, then GW allocates
IPv6 to the device and not the IPv4.
• As of now only 5000 TAC could be listed for whitelisting.
• As there are so many devices being identified and tested which need to be defined in the TAC white
listing, this number need to be increased.
• From package 8.0.0 the TAC which could be whitelisting is being increased to 10,000

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 72

TAC based barring in SAE-GW
Description
• Purpose of this is to bar the services in a given TAC Area as per the regulatory requirement
• The moment UE moves out of the specified TAC, the services will be unbarred.
• This will be implemented using SAE-GW and PCRF.
• In the present scenario, this is achieved by using PCRF only.
• But this requires, the subscriber to be purged and force a Re-ATTACH
• This increases the TPS on PCRF side (Gx in particular)
• After enabling this feature,
• PGW will send CCR-U to PCRF whenever a TAC is barred for all existing subscribers in a specific TAC
• The PCRF thereafter will push the PCC rule (to bar the services) in CCA-U message.
• The SAE-GW will enforce policies as per the PCC rule.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 73

Selection of Virtual APN based on CC
Description
• Virtual APN allows the SAE-GW / P-GW select a specific APN or ability to select different
APN based upon specific information of each session e.g.
• Roaming type
• PEER node address
• RAT type

• With this feature, a new parameter (Charging Characteristic - CC) is added for PGW to
select the Virtual APN

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 74

Supporting TOS feature in TFT
Description
• For iRelay implementation, DSCP is used to distinguish the Bearer and control packet flow.
• Packet of different services have different DSCP values with same 5 Tuples.
• When SAEGW receives any packet, SAEGW selects the bearer with matching Pre-defined
PCC rule based on DSCP value to forward the packet.
• Internal table will be maintained in GW to map PCC / Bearer based on DSCP value.
• Once GW receives the Downlink packet, it searches the table for matching pre-defined PCC rule /
bearer to forward the packet. If there is no match found, default bearer will be selected.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 75

Include Last Cell id in Offline CDR
Description
• To meet the regulatory requirement, this feature will record and update the last User
Location Information AVP of the CDR when the call is released.
• GW will send the last User Location Information AVP to the CDR (SGW-CDR or PGW-CDR)
that is received from MME when the call or bearer is released.
• When ULI is received from the MME through the Delete Bearer Response (DB_RSP)
message and the Delete Session Request (DS_REQ) message, the ULI value is recorded in
the Last User Location Information AVP of the CDR and transmitted.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 76

LMA feature Enhancement
Description
• LMA (Local Mobility Anchor) feature is implemented for the Enterprise customer.
• By default the subscriber authentication is ON.
• With this feature, flexibility will be provided to turn ON or OFF the AAA authentication.
• This will be controlled by GLMA_AUTH parameter added in APN-CONFIGURATION.
• This parameter can be configured as ON or OFF.
• When this parameter is turned on, the authentication for GLMA session will be performed, else it
will be skipped.
• For a new GLMA call with Authentication ON,
• Authentication procedure, (Access-Request /Access- Response messages), will be triggered to AAA server.
• With Authentication configured as OFF, these messages will be skipped.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 77

Session handling during S1-U LAG failure
Description
• As per current way of implementation,
• If all S1U ports of SAEGW are down then
• SAE- GW assigns GTPC IP (S11 IP) to MME instead of GTPU (S1U) interface IPs in “Create Session
Response” (CSRsp) and
• MME was forwarding this S11 IP to eNB for GTPU tunnel establishment.
• UE receives the S11 IP (GTPC IP assigned instead of GTPU (S1U) interface IPs) as a bearer IP and
• UE keep trying to communicate over S11 IPs during that period
• Only way to come out of this is implicit detach and re-attach
• This was impacting the customer experience
• Following changes are implemented in this feature
• If all of the S1-U LAGs are down, the SEAGW shall send failure in "CSRsp" to the MME for the new
session.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 78

Inline Software Upgrade Phase 1
Jio can choose one of below Online upgrade mechanisms
1. Interim solution : Restart system with keeping sessions
• Advantage : Simplest step during PKG Upgrade
• Limitation :
• Active user’s session will be moved to other MMEs in the same pool by UE’s behavior
• Not applicable when F/W need to be changed, but there will be no F/W upgrade between R8.0(2018 2Q)
and R9.0(2019 2Q)

2. Final solution : Graceful in-line upgrade

• Advantage :
• No traffic offload, No service outage
• applicable even when F/W need to be changed
• Limitation :
• The incoming message are to be discarded for 50% of the existing sessions during upgrade time. Therefore,
it is impossible to setup new Volte call during this time. (2 mins for S/W upgrade, 5 mins for F/W upgrade)
• PKG Plan : R9.0(2019 2Q)

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 79

Interim solution: Restart system (keeping sessions)
Concept
• Use “Session Keep” option in the PKG Upgrade command
• During the system restart time, all sessions can be remain in the same system in case of
SAEGW. idle sessions can be remain in the same systems in case of MME
• the new calls during system restart time(approximately 2 min) can be processed by another
system in the same pool
Advantage
• Simplest step to apply during PE and can be provide earliest
• No traffic offload step required
Limitation
• Active user’s session will be moved to other MMEs in the same pool by UE’s behavior (the
number of active user’s session will not be much during PE window)
• All incoming messages will be dropped during PKG Upgrade (approximately 2 min). In case of
UE initiated messages except Service Request, it will lead to fresh Attach
• All traffic will be dropped during PKG Upgrade (approximately 2 min)
Resolution Plan
• It will be updated in EPC 8.0.0 (2018 2Q)

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 80

Inline Upgrade for EPC (Final Solution)

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 81
EPC upgrade : Graceful way without traffic offload
Approach
• Restart CARD one by one in each LESA/LEDA group sequentially to restore sessions.
• Block the communication between LENA (New Package) and LESA/LEDA (Old Package)
Advantage
• Applicable for Software only and total package (software + firmware) upgrade
• Does not require traffic offload.
• It takes ~ 4 Hrs. for offload and bring back the traffic for six GW (in parallel). This time is saved.
• Existing voice and data services continue as it is
• No impact on the volume reporting to OCS and OFCS
• Fresh Attach allowed during the upgrade process
Limitation
• For a maximum 5 min period (2 min for Software only and 5 min for total (Software + Firmware) as
the case may be ), it will not be possible to initiate a new voice call.
Resolution Plan
• It will be available during 2Q ‘19

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 82

EPC upgrade : Graceful in-line method
Mechanism
LENA LESA(LEDA) LESA(LEDA) Step 1.
 Restart all standby CARDs and apply new package
(A) (S) (A) (A) (S) (A) (A) (S)  Sessions will be copied from active to standby cards
Old New Old Old New Old Old New automatically.

Traffic
Step 2.
LENA LESA(LEDA) LESA(LEDA)  Restart one of active CARDs (each LESA/LEDA
group)
 Apply new package.
(S) (A) (S) (A) (A) (S) (A) (A)
 Sessions will be restored by newly activated CARD.
New New New Old New New Old New
 Block communication to the CARDs (old package)
and forward new attach to the CARDs (new pack-
age)
Traffic
LENA LESA(LEDA) LESA(LEDA) Step 3.
 Restart the other of active CARDs (each LESA/LEDA
group)
(S) (A) (A) (S) (A) (A) (S) (A)
 Apply new package.
New New New New New New New New
 Sessions will be restored by newly activated CARD.
 Restore blocked communication between CARDs

Traffic
2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 83
12. Destination IP based dedicated bearer creation
Description
• The Flow Detect function is one of the Flow Action functions of the PCC Rule and operates as
follows:
• When there is a packet detected in the PCC Rule for Flow Detect, it will create a Dedicated
Bearer.
• GW creates a dynamic PCC rule of the flow and bind it to the Dedicated Bearer.
• After that, the corresponding user traffic is served by newly created Dedicated Bearer.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 84

Voice Over Wi-Fi

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.

2016 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 85
Vo Wi-Fi
Key Points
• Data Traffic increasing day by day as the affordability becoming a reality
• In addition to data offload Industry has developed the traction for Voice over Wi-Fi also
• Potential opportunity to convert each Access Point into Cellular node (BTS/NB/eNB/NR)
• Protection of the investment
• The existing Core (EPC and IMS) architecture can be used
• Coverage and capacity improvement
• Address the issue faced by the service providers
• Some dependencies on UE side
• More intelligence being Added
• ANDSF (Access Network Discovery Function)
• Regulation Changing
• Indian Regulatory hurdles over

2016 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 86

Vo Wi-Fi – typical Architecture

Wi-Fi calling enables UE to access IMS services over Wi-Fi

• The same way as we use LTE devices as per 3GPP standard

The native dialler on the device is used for both VoWi-Fi and Cellular (VoLTE)

Same MSISDN used for both VoWiFi and Cellulat (VoLTE)

Seamless Mobility across VoWi-Fi and LTE

2016 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 87

Vo Wi-Fi – typical Architecture

Jio LTE
NW

2016 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 88

Vo Wi-Fi – Jio deployment
Reliance has deployed SAMOG and ePDG nodes at the following Locations
• Pair -1
• Noida
• Ahmedabad
• Pair - 2
• Kolkata
• Luknow
• Pair - 3
• Mumbai
• Nagpur
• Pair - 4
• Bangalore
• Hyderabad

2016 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 89

NFV and Virtual EPC

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary.

2017 © Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 90
Architecture Evaluation & Migration Plan

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 91

91/31
Architecture Evolution Roadmap

MME GW vMME vGW-C vGW-U

ser- ser- ser- ser- ser-
vice vice vice vice vice
V V V
O V
O V
O V
M
O M
O M
S M
S M
S M
O ser- ser- ser- ser- ser-
Ap Ap Ap Ap S S S vice vice vice vice vice
p p p p
Hypervisor OS + Container Platform + PaaS
HW HW HW HW
compute network storage compute network storage

Infra Virtualization OS Virtualization (con-

H/W (VMs) tainers)

4G 5G

 Service Based Architecture

 On-Premise Cloud (COTS)
 HW-SW Coupling  Microservice & Cloud Native
 Performance-optimized VNF
 Manual Operation  Stateless
 Automated VNF Orchestration
 E2E Orchestration & Closed-loop
 Microservice started with CUPS
Control

92
EPC VNF Migration from Legacy Network

Today : Legacy EPC Interim : Tput expansion by GW- Target : vGW-U deployment
C/U Separation

MME vMME vGW-C vMME vGW-C

Internet Internet Internet

eNB eNB eNB vGW-U

UE UE GW-U UE GW-U
SAE GW

Flexibility and capacity expansion

Legacy MME, SAE GW with the separation of GW control Full network slicing for IoT, MVNO,
plane and user plane Enterprise Private LTE

• Deploy cost-effective HW • Separate GW-U (vGW-U or HW

accelerator GW-U Accelerator GW-U) according to
• Re-use existing A-EPC HW for service type or business type
GW User Plane
NFV/SDN Solution Overview

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 94/31

Samsung Networks NFV Focus Areas
Internet Of Things
Virtual RAN Virtual Core Public Safety
(IoT)

 Virtual RAN  LTE core functions  Compact systems  Service & Solution Platform
 Virtual small cell solution  IMS core functions  Public safety virtual core for Vertical Market
 Management systems  Network services and applications  Scalable separate and com-
 Charging functions bined control/user planes
 Subscription and Policy

Orchestration and
Analytics Future 5G Network vEPC
Management

 Access agnostic core  Interworking with existing

 VIM, VNFM, NFVO  RAN, Core and Services  Control/User plane separa- network & easy migration
 Network controllers analytics driving automa- tion to EPC VNF
tion and management.  Network Slicing  Feature Parity with Legacy
 End to end Service control
Service

Priority Solutions
Migration to NFV Platform (Samsung NFV VNFs)
Provides NFV migration from Current Telco Systems/Applications
Supports legacy feature set on common NFV Platform
NFV Management by Samsung Cloud Management Solution (CMS)
IMS AS

… [ NFV based Compact Core ]

TAS VMIG RCS PTT
(VCC/IP-SM-GW)
CMS
IMS Core Common EMS NFVO

VCC-AS/
TAS IP-SM-GW
RCSe WebRTC
ENUM/
HSS/SPR MNP
PCRF PTT
C-HSS/SPR PCRF CSCF MGCF DRA
MGCF CSCF OFCS/OCS VNFM

… MRF A-SBC I-SBC

SBC/AGW MME S-GW P-GW VNFs

MRF MGW
NFV Infrastructure
EPC MBMS/M2M
COTS VIM

Compute Storage Network

MME/SGSNS-GW/P-GW/GGSN MBMS GW MTC-IWF

Samsung NFV Scope & Deployed Architecture
Provides NFV migration from Current Telco Systems/Applications
Supports legacy feature set on common NFV Platform
Virtual Network Functions (VNFs) providing software applications for EPC
(MME, SAE GW) and IMS (CSCF, TAS, PCRF, IP-SM-GW, and SBC)
Ve-VnFm Samsung Cloud Management Solution (CMS)
EMS
Samsung NFVO

VNFs

vEPC vIMS
VNFC VNFC
···

···

Samsung VNFM
VNFC VNFC

Controller
OS / Hypervisor
Nf-Vi Samsung
COTS Virtual Infra Manager
(VIM)
Compute Storage Network
Physical Infra
Manager (PIM)
North Bound Integration

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 98/31

NFV Component Scope
Samsung will provide vEPC (vMME, vGW-C, vGW-U), vCIoT, CSM and CMS (MANO)
Samsung MANO and CSM(EMS) Interworks with Jio MSO

Jio MSO

NFV Management

CMS (MANO) CSM * SW upgrade

vEPC vCIoT
vGW-C
vMME vGW-U vCIoT
MSO : Master Service Or-
chestrator
CSM : Core System Man-
agement
CMS : Cloud Management
System
CIoT : Cellular IoT
MANO: NFV Management
and
99
Integration to MSO
• MSO and Samsung Solution have hierarchical architecture
• Samsung NFVO provides VNF’s lifecycle and local infrastructure orchestration
• Samsung EMS provides NE’s configuration, fault, performance management

MSO

NFVO EMS NFVO EMS

100
Samsung Solution NBI
• The Group of APIs provided is as follows :
 VNF Lifecycle management
 VNF Configuration, Fault , Performance management
 PNF Configuration, Fault, Performance management
 Periodic interface for bulk file transfer

MSO

VNF PNF Alarm Periodic

Lifecycle Configuration Interface Interface

Lifecycle Configuration Performance Fault

Management Management Management Management

Samsung Solution

VNF / PNF / Infrastructure

101
Backup Slides

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 102

102/31
MANO

© Samsung Electronics. All Rights Reserved. Confidential and Proprietary. 103/31

MANO Main Features
• NFVO
 VNF/NS Lifecycle Orchestration
 NFVI Resource Management VNF Package
 VNF Package Management On-Boarding

• VNFM
 VNF Lifecycle Management VNF Termina- VNF Instantia-
tion tion
 VNF Performance Management
 VNF Fault Management
• VIM
VNF Monitor-
 VNF Scaling
Software Image Management ing
 Virtualized Resource Management
 Virtualized Resource Performance/Fault Management
[ VNF Lifecycle ]
• PIM
 Physical Resource Performance Management
 Physical Resource Fault Management
Difficulties in Troubleshooting
Disaggregated Vendor Single Vendor

NFVO VNFM Opensta

VNF NFVO VNFM PIM
ck

Opensta
VNF
ck

Switch PIM

Storage Server Switch Storage Server

 Operator to integrate multiple SW and HW vendors’

products
 Less layers – commodity HW and NFV SW
 Operator coordinates all things, including root cause
 Simpler operation
analysis, during troubleshoot
 It takes much time and endeavor
105
Samsung MANO
• MANO solution for lifecycle management of VNF
• Elements of basic management are the same, but there are differences in how to
manage efficiently.
Preparation
Stage
Destroy Design

Healing Deploy

Operation Resource Management

Stage
Monitoring

106
Copyright and Confidentiality
Copyright © 2017, SAMSUNG Electronics Co., Ltd. SAMSUNG Electronics reserves the right to make changes to the specifications of the
products detailed in this document at any time without notice and obligation to notify any person of such changes. Information in this
document is proprietary to SAMSUNG Electronics Co., Ltd. No information contained here may be copied, translated, transcribed or duplicated
by any form without the prior written consent of SAMSUNG Electronics.