Accuver NB-IoT Solutions

November 2017
Why Accuver NB-IoT Solutions

• Reduce costs and time scales for test and verification process
• By Automating UDP, Ping, and Iperf, test cases, removing manual test elements
• Increase test accuracies through automation
• Generating automated statistics
• Using NB-IoT upgrades to existing XCAL-M and XCAP-M platforms
• Combining analysis of NB-IoT, L1/L2 Major KPIs with L3 (RRC/NAS)
• Using NB-IoT upgrades to existing XCAL-M and XCAP-M platforms, means no new
investment required for specialised tools and or training
• Using XCAP-M’s analytics to rapidly diagnose issues and carryout root cause analysis
• Customised XCAP-M Reporting means rapid analysis in vendor trials

2
 Internet Of Things CY 2016 CY 2017
SigFox
LPWAN
LORA
Cellular IOT
3GPP LTE LTE-M NB-IOT

*LPWAN: Low Power Wide Access Network

SigFox LoRa Rel 12 Rel 13

Network type Cellular Cellular LTE-M NB-IoT
Frequency ISM(under 1GHz) ISM(under 1GHz) DL/UL Max speed 1Mbps/1Mbps 100kbps/100kbps
MIMO no no
Modulation/M GMSK(UNB)/no Chirp FM+Spread
ultiple Access Factor 12~8 DL/UL duplex Half FDD Half FDD
Bandwidth 1.4MHz(6RB) 200kHz/1RB
Sensitivity -138dBm -138dBm
UE Max. power ~20dBm ~20dBm
DL/UL Support UL only DL/UL
15kHz or
Sub carrier spacing 15kHz
Ack No yes 3.75kHz
LTE Compatibility yes yes
Adaptive Rate No yes
LTE in-band or Guard
Data Rate 100~300bps 300~50kbps Working band LTE in-band band or
Specific band
Mobility Bad Good
3
NB-IoT System Overview

4
Accuver NB-IoT Test Domain – Use Cases

• NB-IoT Device performance benchmarking

• NB-IoT Device performance envelope definition
• NB-IoT Systems performance benchmarking
• NB-IoT System performance envelope definition
• NB-IoT Device Connectivity performance verification
• NB-IoT Device power consumption verification under
• Basic connectivity scenarios
• Differing test scenarios
• Differing System configurations
• Differing RF conditions (e.g. within Cell and Cell Edge)

• Impact of latency on NB-IoT Systems and device performance

5
 Completed: (C)
XCAL chipset roadmap Dropped: (D)
Pending: (P)

1H 2017 3Q 2017 4Q 2017 1H 2018

End of June End of September End of December End of June

• 5G(S/W & H/W) Phase1 (C)
• NB-IOT (C)
- HiSilicon : DM Message (C)
- Qualcomm (9606) (C)
• LoRA IOT (C)
- SEMTECH
(SX1272LM1CEP) (C)
- Support NOKIA FW (C)
• Qualcomm SD835 (X16 LTE
Modem): LTE Cat.16(DL), 4CA,
1.0Gbps(DL), Up to 4x4 MIMO
on two carriers (C)
• Samsung Exynos 9
Series(8895) : LTE Cat.16(DL),
5CA, 1.0Gbps(DL) (C)
LTE only:
• HiSilicon(Balong720): Cat6 :
Huawei P9/P9+ (C)
• GCT: GDM7243M (C)
GDM7243Q (C)
• NB-IOT • 5G(S/W & H/W) Phase2 • LTE
- HiSilicon (Neul) : - Qualcomm SD845 (X20
Specification update • LTE LTE Modem): LTE
- Intel: XMM7480 Cat.18(DL), 5CA,
- Qualcomm(9606):
Specification update - GCT: GDM7243A(8RX) 1.2Gbps(DL), Up to 4x4
MIMO on three carriers
• LTE - Samsung Exynos Series :
- HiSilicon(Balong750): LTE Cat.18(DL), 6CA,
LTE Cat.12(DL), 1.2Gbps(DL)
4x4MIMO (P)
• NB-IOT
- Sequans Cat-M1/NB1
- Altair(ALT1250): Cat-
M1/NB1
- Intel(XMM7115M): NB1
• Scanner
- PCTEL NB-IOT Scanner
- R&S NB-IOT (TMSW,
TSME) Scanner

6
NB-IoT Test Module (sample)

• NB-IoT Test Module not supplied by Accuver

7
Accuver NB-IoT Test Domain – XCAL-M
• Using Accuver NB-IoT software module option to XCAL-M platform to interface to NB-IoT test device

• Control automated tests

• Display and record test
NB-IoT Test device results to view in XCAP

XCAL

8
Qualcomm Chipset NB-IoT/eMTC - LTE Cat-M1 /LTE Cat-NB1 Device

Qualcomm (QC) MDM9206 Chipset based

High performance / Low Power consumption
(70mm x 33mm x12mm)

Please note that this

device has not yet
been CE Certified

9
NB-IoT – Qualcomm

Current State
1. KPI
- Application of Qualcomm ICD Version YYU (October 4, 2017) is completed.
2. In case of Qualcomm, since both CAT-M1 and NB-IoT are supported, all items excluding PHY are
commonly applied.
3. Autocall support
- Uplink Data Trans, Ping, PS (Attach/Detach)
- All existing Autocall types are supported for the UE models supporting QMICM and Modem.

Further Study
1. Development of Chipset Type for NB IoT only
Expected Benefit: To eliminate complexity of KPI with all existing LTE
2. Development of AOF

10
Autocall – UL Data Trans for Qualcomm

• Autocall UL Data Trans transfers the uplink UDP data for NB IoT Qualcomm chipset
for selected Traffic Time.

UE Destination

Interval
Repeat
Count
Parameter Description
Repeat Count Repeat count for transferring Uplink Data
Interval Repeat Interval for Second
Data Length(byte) Data length for byte (Greater than 21 byte)
CID A numeric parameter which specifies a
particular PDP context or EPS bearer context
definition

11
Autocall – PING (AT) for Qualcomm

• Autocall Ping measures latency performance for NB-IoT Qualcomm chipset.

UE Destination IP

Timeout
Repeat in Traffic time
ICMP Response

Interval

Timeout
ICMP Response
Parameter Description
IP Address Address of sending the message in IPv4
format
Interval Interval after PING response
Size(Byte) Size of echo packet payload in range 8~1460
bytes.
Timeout(msec) Maximum time to wait for end echo reply
response in range 10~60000 msec
Success Ratio(%) Response / Request * 100 in Traffic time

12
Neul Hisilicon Chipset NB-IoT Device

High performance / Low

Power consumption
(70mm x 33mm x12mm)

Please note that this

device has not yet
been CE Certified

13
NB-IoT – Neul Hisilicon

Current State
1. Status of UE sync
- UE sync is managed separately due to discrepant parser per Mobile Version.

Mobile Version Interface Parsing KPI Autocall

V100R100C10 B656 O O O O
V100R100C10 B656SP1 O O Partially Complete O
V100R100C10 B657SP1 O O Partially Complete O
V100R100C10 B657SP2 O O(not checked) Partially Complete O

2. Autocall support
- PING, Uplink Data Transfer (UDP), PS (Attach/Detach).
- All Autocall test is controlled by AT Command only.

Further Study
1. Improvement of KPI per Mobile Version
2. Development of AOF

14
Autocall – UL Data Trans for Neul Hisilicon

• Autocall UL Data Trans transfers the uplink UDP data packets for NB IoT Neul chipset for
selected Traffic Time.

UE Destination IP

Interval
Repeat
Count
Parameter Description
Repeat Count Repeat count for transferring Uplink Data
Interval Repeat Interval for Second
Data Length(byte) Data length for byte (Maximum data size is 512
bytes)
Destination IP address is supported only IPv4
Address(IPv4)
Destination Port A number in the range 0-65535. This is the
remote port that messages will be received on
15
Autocall – PING (AT) for Neul Hisilicon

• Autocall Ping allows to measure latency performance for NB IoT Neul chipset.

UE Destination IP

Timeout
Repeat in Traffic time
ICMP Response

Interval

Timeout
ICMP Response
Parameter Description
IP Address Address of sending the message in IPv4 format
Interval Interval after PING response
Size(Byte) Size of echo packet payload in range 8~1460
bytes.
Timeout(msec) Maximum time to wait for end echo reply response
in range 10~60000 msec
Success Ratio(%) Response / Request * 100 in Traffic time

16
XCAL-M Port Setting NB IoT Radio Parameters
(Hisilicon Neul example)

17
XCAL-M NB-IoT Serving Cell Graphs, Parameters and L3 Messages

18
XCAP-M NB-IoT Analysis Across multiple views and information elements

19
XCAP-M NB-IoT Neul Main Parameter NB-IoT Signalling Message

20
Power Consumption Test Case – Smartphone Test device used for illustration

Summary Report for each call shall be provided

• 1. Power Consumption Average [Idle]
• 2. Power Consumption Average [Call Time] ; average between call start and call end
• 3. Power Consumption Average [Traffic Time] : average during the traffic status, i.e. excluding call setup
stage data

21
Your partner in
network performance

22