LTE

Internet of Things Seminar

CONFIDENTIAL
Slide 1 © 2016 AT4 wireless - a DEKRA company
Contents

► LTE for IoT

► Category 1
► Category 0
► Release 13
► Narrow Band IoT
► Comparison
► 3GPP
► GCF, PTCRB, GSMA
► Adoption
► Testing @ AT4

Slide 2 © 2016 AT4 wireless - a DEKRA company

Slide 3 © 2016 AT4 wireless - a DEKRA company
 LTE for IoT

► Known as LTE-M, LTE for M2M…

► Category 1: Compatible with existing
LTE networks and spectrum allocations
► Category 0: Some high-layer
adaptations required
► Categories M, NB: Further evolution
planned for Release 13, narrow band
requires substantial changes in network
side

Slide 4 © 2016 AT4 wireless - a DEKRA company

Slide 5 © 2016 AT4 wireless - a DEKRA company
Slide 6 © 2016 AT4 wireless - a DEKRA company
 Category 1
No need to wait for Cat 0

LTE category 1 was defined in the original 3GPP LTE specifications of 2008, along with
categories 2, 3, and 4, but because operators and device makers were focused primarily on
the needs of high-speed smartphones and category 3 and 4 technology, category 1 was
overlooked. The rapid spread of LTE networks and the inevitable sunsetting of 2G and 3G
networks, has completely changed the scene. lt is now universally accepted that LTE will be
used for nearly everything that requires a wireless connection, including M2M and loT
applications where it was once deemed too expensive and complex - Cat 1 LTE solutions
shatter this perception and take on tremendous new importance.

Slide 7 © 2016 AT4 wireless - a DEKRA company

 Amsterdam, January 6, 2016 – Gemalto, the world leader in digital secutiry, has won
the Most Innovative LTE Application and Service Award for its Cinterion® Cat 1 LTE
wireless module. The prestigious award improving the future of cellular networks
throughout the region. The Gemalto solution was selected for enabling highly efficient
connectivity over LTE networks for purpose designed Machine-to-Machine (M2M) and
Internet of Thing (IoT) solutions needing mid-tier speed while requiring the longrvity
and reability of LTE.
Sony Corporation ("Sony") is announcing that it has
reached an agreement with Altair Semiconductor
acquired by ("Altair") and its major shareholders to acquire the
company. Sony expects to complete the acquisition
in early February, 2016.
HOD HASHARON, Israel – November 30, 2015 – Altair Semiconductor (www.altair-semi.com), a leading
provider of LTE chipsets, today announced its FourGee-1160 Category 1 (CAT-1) chipset has been selected
by Korea Telecom (KT) to provide ultra-low power LTE connectivity for three Internet of Things (IoT) use cases
on exhibit at the “KT Internet of Small Thing” Event in Korea las week.
Chipset Solution for Category 1 LTE Devices for the Internet of
Things (IoT)

The Calliope LTE Platform for IoT is a member of Sequans´

StreamliteLTE family os the LTE chipset products. Calliope comprises
baseband and RF chips, an integrated IoT applications processor
running Sequans´carrier-proven LTE protocol stack, and IMS client,
and a comprehensive software package for over-the-air device
management and packet routing. It includes Sequans´powerful
interference rejection technology. Sequans AIRTM.

Slide 8 © 2016 AT4 wireless - a DEKRA company

 Category 0
► Low device cost
► Long battery life
► Enhanced coverage
► Network signaling

Non Critical Extension SEQUENCE UECAT0

SIB1
Cell Access Related Info – v 12 xy
SEQUENCE
Category 0 Allowed –r 12 True Cat 0 Allowed

A low complexity UE may access a cell only if SIB1 indicates that access of low
complexity UEs is supported. If the cell does not support low complexity UEs, a low
complexity UE considers the cell as barred.

The eNB determines that a UE is a low complexity device based on the LCID for CCCH
and the UE signalled capability.

Slide 9 © 2016 AT4 wireless - a DEKRA company

 3GPP TS 36.331
► UE Capability indication of category 0

UE-EUTRA-Capability-v1250-IEs ::= SEQUENCE {

ue-CategoryDL-r12 INTEGER (0..14) OPTIONAL,

ue-CategoryUL-r12 INTEGER (0..13) OPTIONAL,

}
► UE-RadioPagingInfo IE for category 0

UE-RadioPagingInfo-r12 ::= SEQUENCE {

ue-Category-v1250 INTEGER (0) OPTIONAL,
...,
[[ ue-CategoryDL-M-v1310 ENUMERATED {m1} OPTIONAL,
ce-ModeA-r13 ENUMERATED {true} OPTIONAL,
ce-ModeB-r13 ENUMERATED {true} OPTIONAL
]]

}
Slide 10 © 2016 AT4 wireless - a DEKRA company
► Release 12 introduces Power Saving Mode
► Battery life depending on Tracking Area Update (TAU) cycle and transaction cycle

Slide 11 © 2016 AT4 wireless - a DEKRA company

► Power Saving Mode definition
► Similar to power-off, but the UE remains registered with the network
► No need to re-attach or re-establish PDN connections
► A UE in PSM is not immediately reachable for mobile terminating services
► A UE using PSM is available for mobile terminating services only for the period of an
Active Time after a mobile originated event like data transfer or signaling, e.g. after a
periodic TAU/RAU procedure
► Intended for UEs that are expecting only infrequent mobile originating and terminating
services and that can accept a corresponding latency in the mobile terminating
communication
► No support in the CS domain on the network side
► Should only be used by UEs using the PS domain, SMS and mobile originated IMS or CS
services
► A UE that uses mobile terminated IMS or CS services other than SMS should not use
PSM as neither IMS nor the CS domain provide support for mobile terminated CS voice
or IMS services to UEs that are in PSM
► Power Saving Mode procedure
► When the UE wants to use the PSM it shall request an Active Time value during every
Attach and TAU/RAU procedures
► If the network supports PSM and accepts that the UE uses PSM, the network confirms
usage of PSM by allocating an Active Time value to the UE. The network takes the UE
requested value and any local MME/SGSN configuration into account for determining the
Active Time value that is allocated to the UE
► If the UE wants to change the Active Time value, e.g. when conditions are changed in the
UE, the UE consequently requests the value it wants in the TAU/RAU procedure

Slide 12 © 2016 AT4 wireless - a DEKRA company

► Power Saving Mode Timers
T3324 / T3412
► Proposed by device and
confirmed by network

3GPP 24.301
3GPP 23.682

Slide 13 © 2016 AT4 wireless - a DEKRA company

 ► Multiplexing
► FDD Full Duplex
► FDD Half Duplex
► New for Cat. 0
► TDD

Slide 14 © 2016 AT4 wireless - a DEKRA company

The lndustry's Most Advanced LTE Category 0 Chipset Solution

The FourGee-11 50/6401 is an LTE Category-0 chipset featuring downlink speeds of up to 11 Mbps,
extremely low power consumption, and a disruptive price tag_ This loT- optimized chipset is highly
integrated and incorporates elements such as an advanced on-chip power management unit, integrated
DDR memory and a low power MCU subsystem with a robust security framework for customer
developed applications.
Featuring a rich set of host, peripheral and sensor interfaces, the FourGee-11 50/6401 is ideal for
integration in applications such as wearables, smart meters, lighting, parking and traffic control, vending
machines and other low-bitrate and battery-operated loT devices.

For the demonstration at Super Mobility Week, created in partnership with

Ericsson. Sequans is using a software-modified version of its Calliope CAT 1
LTE platform. to demonstrate Release 12. CAT 0 features. These include half-
duplex operation and reduced peak throughput both of which result in lower
cost smaller footprint modules and reduced power consumption.

Slide 15 © 2016 AT4 wireless - a DEKRA company

 Release 13
► Categories M1, M2 The target for IoT connectivity link budget
is an enhancement of 15-20 dB.
► Reduced bandwidth The coverage enhancement would typically
be equivalent to wall or floor penetration,
► Reduced power class
enabling deeper indoor coverage.
► Reduced complexity
Cat. M1 Cat. M2

Although an upgrade to Cat 0 is supported, Altair is "not a big believer"

in the technology, seeing it as a stopgap on the way to Cat M, which
he estimated will be in devices in the market by the end of 2017 after
LTE Release 13 is finalized. Cat M supports much greater power
efficiency gains and limits throughput speeds to just 375 Kbps.

Slide 16 © 2016 AT4 wireless - a DEKRA company

 3GPP TS 36.331
► UE Capability indication of category M1

UE-EUTRA-Capability-v1310-IEs ::= SEQUENCE {

ue-CategoryDL-v1310 ENUMERATED {n17, m1} OPTIONAL,

ue-CategoryUL-v1310 ENUMERATED {n14, m1} OPTIONAL,

}
► UE-RadioPagingInfo IE for category M1

UE-RadioPagingInfo-r12 ::= SEQUENCE {

ue-Category-v1250 INTEGER (0) OPTIONAL,
...,
[[ ue-CategoryDL-M-v1310 ENUMERATED {m1} OPTIONAL,
ce-ModeA-r13 ENUMERATED {true} OPTIONAL,
ce-ModeB-r13 ENUMERATED {true} OPTIONAL
]]

}
Slide 17 © 2016 AT4 wireless - a DEKRA company
 3GPP TS 36.306
► Category M1 parameters
► Maximum number of DL-SCH transport block bits received within a TTI = 1000
► Maximum number of bits of a DL-SCH transport block received within a TTI = 1000
► Total number of soft channel bits = 25344
► Maximum number of supported layers for spatial multiplexing in DL = 1
► Maximum number of UL-SCH transport block bits transmitted within a TTI = 1000
► Maximum number of bits of an UL-SCH transport block transmitted within a TTI = 1000
► Support for 64QAM in UL = No
► Total layer 2 buffer size [bytes] = 20000
► With support for split bearers = N/A
► Half-duplex FDD operation type = Type B
► Maximum UE channel bandwidth [PRB] = 6
► Coverage enhancement mode A = Mandatory

Slide 18 © 2016 AT4 wireless - a DEKRA company

 3GPP TS 36.211
► Category M1 physical layer 3GPP TS 36.213

► New channel: MPDCCH (MTC physical downlink control channel)

► Similar to EPDCCH but with different cycle prefix allocation depending on
subframe type and different subframe formats
► Use of special subframes depend on coverage enhancement mode (CEMode)
used
► Coverage enhancement modes A (Mandatory) and B (Optional)
► Nacc for scrambling
► Mapping to physical resources
► Mapping of PUSCH/PUCCH
► Interpretation of Random Access Response Grant
► PDSCH processing procedures
► Channel State Information processing procedures
► PUSCH/PUCCH transmission procedures
► Monitoring of MPDCCH
Slide 19 © 2016 AT4 wireless - a DEKRA company
 Narrow Band IoT
► NB-IoT = Category NB1
► Narrow Band implementation
► For scenarios where very narrow spectrum allocation is available
► 200 kHz BW has been proposed – allows coexistence with GSM channels
► Requires substantial changes in network side
► 3GPP Work Item

Slide 20 © 2016 AT4 wireless - a DEKRA company

 Narrow Band IoT

Slide 21 © 2016 AT4 wireless - a DEKRA company

 3GPP TS 36.331

► NB-IoT is a non backward compatible variant of E-UTRAN supporting a reduced set of

functionality. Parts of procedures and messages specified for the UE equally apply to
the UE in NB-IoT. There are also some features and related procedures and messages
that are not supported by UEs in NB-IoT.
► Handover, interRAT, Carrier Aggregation, public warning systems, CS fallback,
WLAN interworking, emergency calls, etc.
► In regard to mobility, NB-IoT is a separate RAT from E-UTRAN.
► Parts of procedures and messages are only applicable to UEs in NB-IoT.
► For NB-IoT, mobility between E-UTRA and UTRAN, GERAN and between E-UTRA and
CDMA2000 1xRTT and CDMA2000 HRPD is not supported.

Slide 22 © 2016 AT4 wireless - a DEKRA company

 3GPP TS 36.331

► Specific NB-IoT RRC messages

► MasterInformationBlock-NB ► RRCConnectionResume-NB

► SystemInformationBlockTypeX-NB ► RRCConnectionResumeComplete-NB

► X = 1, 2, 3, 4, 5, 14,16 ► RRCConnectionRequest-NB

► Paging-NB ► RRCConnectionResumeRequest-NB

► DLInformationTransfer-NB ► RRCConnectionSetup-NB

► RRCConnectionReconfiguration-NB ► RRCConnectionSetupComplete-NB

► RRCConnectionReconfigurationComplete-NB ► SystemInformation-NB

► RRCConnectionReestablishment-NB ► UECapabilityEnquiry-NB

► RRCConnectionReestablishmentComplete- ► UECapabilityInformation-NB
NB
► ULInformationTransfer-NB
► RRCConnectionReestablishmentRequest-NB

► RRCConnectionReject-NB

► RRCConnectionRelease-NB

Slide 23 © 2016 AT4 wireless - a DEKRA company

 3GPP TS 36.331
► UE Capability indication of category NB1

UE-Capability-NB-r13 ::= SEQUENCE {

accessStratumRelease-r13 AccessStratumRelease-NB-r13,
ue-Category-NB-r13 ENUMERATED {nb1} OPTIONAL,
multipleDRB-r13 ENUMERATED {supported} OPTIONAL,
pdcp-Parameters-r13 PDCP-Parameters-NB-r13 OPTIONAL,
phyLayerParameters-r13 PhyLayerParameters-NB-r13,
rf-Parameters-r13 RF-Parameters-NB-r13,
nonCriticalExtension SEQUENCE {} OPTIONAL
}

► UE-RadioPagingInfo IE for category NB1

UE-RadioPagingInfo-NB-r13 ::= SEQUENCE {

ue-Category-NB-r13 ENUMERATED {nb1} OPTIONAL,
...
}

Slide 24 © 2016 AT4 wireless - a DEKRA company

 3GPP TS 36.306
► Category NB1 parameters
► Maximum number of DL-SCH transport block bits received within a TTI = 680
► Maximum number of bits of a DL-SCH transport block received within a TTI = 680
► Total number of soft channel bits = 2112
► Maximum number of UL-SCH transport block bits transmitted within a TTI = 1000
► Maximum number of bits of an UL-SCH transport block transmitted within a TTI = 1000
► Total layer 2 buffer size [bytes] = 4000
► Half-duplex FDD operation type = Type B
► New ROHC profiles
► New physical layer parameters = multiTone-r13, multiCarrier-r13
► New RF parameters: supportedBandList-r13, powerClassNB-20dBm-r13
► New general parameter: accessStratumRelease-r13

Slide 25 © 2016 AT4 wireless - a DEKRA company

 3GPP TS 36.201
► Category NB1 physical layer 3GPP TS 36.211

► Sub-carriers downlink: 12 sub-carriers with a sub-carrier bandwidth of 15kHz

► Sub-carriers uplink: single sub-carrier with a sub-carrier bandwidth of either 3.75kHz or
15kHz (alternatively 3, 6 or 12 sub-carriers with a sub-carrier bandwidth of 15kHz)
► New uplink modulations: π/2 BPSK and π/4 QPSK for single sub-carrier NB-IoT
operation
► New channels:
► NPDCCH (narrowband physical downlink control channel)
► NPDSCH (narrowband physical downlink shared channel)
► NPBCH (narrowband physical broadcast channel)
► NPRACH (narrowband physical random access channel)
► NPUSCH (narrowband physical uplink shared channel)
► New reference signals:
► NPSS (narrowband primary synchronization signal)
► NSSS (narrowband secondary synchronization signal)
► NRS (narrowband reference signal)
Slide 26 © 2016 AT4 wireless - a DEKRA company
 3GPP TS 36.213
► Category NB1 physical layer 3GPP TS 36.214

► Modified UE procedures:
► Cell search (NPSS, NSSS)
► Timing synchronization
► Uplink power control
► Downlink power allocation
► Random access procedure
► Reception of NPDSCH
► Reporting ACK/NACK
► Transmission of NPUSCH
► Reception of ACK/NACK
► Reception of NPDCCH
► New physical layer measurements: NRSRP, NRSRQ

Slide 27 © 2016 AT4 wireless - a DEKRA company

 Comparison

Slide 28 © 2016 AT4 wireless - a DEKRA company

 3GPP

► 3GPP RAN Work Item “Low cost & enhanced coverage MTC UE for LTE”
► The work plan overall includes 84 test cases (46 RF, 41 RRM and 6 protocol test
cases)
► Relevant core requirements

TS Title
36.101 E-UTRA and E-UTRAN; User Equipment (UE) radio transmission and reception
36.133 E-UTRA and E-UTRAN; Requirements for support of radio resource
management
36.201 E-UTRA and E-UTRAN; LTE physical layer; General description
36.211 E-UTRA and E-UTRAN; Physical channels and modulation
36.212 E-UTRA and E-UTRAN; Multiplexing and channel coding
36.213 E-UTRA and E-UTRAN; Physical layer procedures
36.300 E-UTRA and E-UTRAN; Overall description; Stage 2
36.302 E-UTRA and E-UTRAN; Services provided by the physical layer
36.306 E-UTRA and E-UTRAN; User Equipment (UE) radio access capabilities
36.321 E-UTRA and E-UTRAN; Medium Access Control (MAC) protocol specification
36.331 E-UTRA Radio Resource Control (RRC); Protocol specification

Slide 29 © 2016 AT4 wireless - a DEKRA company

 ► Examples of Change Requests

3GPP 36.521-1 (RF)

3GPP 36.523-1 (Protocol)

Slide 30 © 2016 AT4 wireless - a DEKRA company

► 6 RRM (3GPP 36.521-3) tests cases were developed by AT4 wireless and were reviewed
and accepted in RAN5 meeting hosted in November 2015

Test Specs TC Name Release Description Tdoc CRNum

36.521-3 9.1.41.1 Rel-12 FD-FDD Intra Frequency Absolute RSRP Accuracy for UE category 0 R5-155770 1330
36.521-3 9.1.41.2 Rel-12 FD-FDD Intra Frequency Relative RSRP Accuracy for UE category 0 R5-155771 1331
36.521-3 9.1.42.1 Rel-12 HD-FDD Intra Frequency Absolute RSRP Accuracy for UE category 0 R5-155772 1332
36.521-3 9.1.42.2 Rel-12 HD-FDD Intra Frequency Relative RSRP Accuracy for UE category 0 R5-155773 1333
36.521-3 9.1.43.1 Rel-12 TDD Intra Frequency Absolute RSRP Accuracy for UE category 0 R5-155774 1334
36.521-3 9.1.43.2 Rel-12 TDD Intra Frequency Relative RSRP Accuracy for UE category 0 R5-155775 1335

Slide 31 © 2016 AT4 wireless - a DEKRA company

 ► Existing test cases are modified to include Category 0 requirements
► For example, RF test cases (3GPP 36.521-1)

Fader_11
SS Tx1 DUT

Fader_21
Tx2

AWGN_1 Tx/Rx
M
Rx

Figure A.0: Reduced Implementation of connections for UE Category 0 testing

(example of Figure A.10)

Slide 32 © 2016 AT4 wireless - a DEKRA company

 ► 3GPP RAN Work Item “NarrowBand IOT (NB-IOT)”
► Relevant core requirements

Spec No.CR Subject of the CR Approved at plenary# Comments

36.300 Introduction of NB-IOT
36.101 Introduction of NB-IOT RAN#71 (Mar’’16) Approval date only applies to core
36.104 Introduction of NB-IOT RAN#71 (Mar’16)’ Approval date only applies to core
36.141 Introduction of NB-IOT RAN#71 (Mar’16)’ Approval date only applies to core
36.133 Introduction of NB-IOT RAN#71 (Mar’16)’ Approval date only applies to core
36.201 Introduction of NB-IOT RAN#71 (Mar’16)’
36.211 Introduction of NB-IOT RAN#71 (Mar’16)’
36.212 Introduction of NB-IOT RAN#71 (Mar’16)’
36.213 Introduction of NB-IOT RAN#71 (Mar’16)’ Supporting operators
36.214 Introduction of NB-IOT RAN#71 (Mar’16)’
36.302 Introduction of NB-IOT RAN#71 (Mar’16)’ AT&T
36.304 Introduction of NB-IOT RAN#71 (Mar’16)’ Deutsche Telekom
36.306 Introduction of NB-IOT RAN#71 (Mar’16)’ Sprint
36.321 Introduction of NB-IOT RAN#71 (Mar’16)’
36.322 Introduction of NB-IOT RAN#71 (Mar’16)’
Telecom Italia SPA
36.323 Introduction of NB-IOT RAN#71 (Mar’16)’ Telefonica
36.331 Introduction of NB-IOT RAN#71 (Mar’16)’ TeliaSonera
T-Mobile US
US Cellular
Verizon
Vodafone

Slide 33 © 2016 AT4 wireless - a DEKRA company

 ► Standarization status
February 2016

Cat. NB1

Slide 34 © 2016 AT4 wireless - a DEKRA company

 GCF, PTCRB, GSMA

Slide 35 © 2016 AT4 wireless - a DEKRA company

 GCF, PTCRB, GSMA
► GCF Conformance Work Items corresponding to category NB1 presented during CAG #44
► Protocol, RF tests
Work Item Type of Test Technology Test Specification Test Case TC Description
WI-257 PCT NB-IoT TS 36.523-1 9.2.4.1.1 Attach and Normal tracking area update Procedure / Success / With and w ithout Idle eDRX parameters
WI-257 PCT NB-IoT TS 36.523-1 9.2.4.1.2 Attach & Normal tracking area update Procedure / Success / w ithout Idle eDRX and PSM parameters /
With Idle eDRX and PSM parameters

Work Item Type of Test Technology Test Specification Test Case TC Description
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.2.2F UE Maximum Output Pow er for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.2.5F Configured UE transmitted Output Pow er for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.3.2F Minimum Output Pow er for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.3.3F Transmit OFF pow er for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.3.4F.1 General ON/OFF time mask for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.3.4F.2 NPRACH time mask for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.3.5F.1 Pow er Control Absolute pow er tolerance for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.3.5F.2 Pow er Control Relative pow er tolerance for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.5.1F Frequency Error for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.5.2.1F.1 Error Vector Magnitude (EVM) for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.5.2.2F Carrier leakage for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.5.2.3F In-band emissions for non allocated RB for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.6.1F Occupied bandw idth for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.6.2.1F Spectrum Emission Mask for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.6.2.3F Adjacent Channel Leakage pow er Ratio for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.6.3.1F Transmitter Spurious emissions for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.6.3.2F Spurious emission band UE co-existence for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 6.7F Transmit intermodulation for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 7.3F Reference sensitivity level for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 7.4F Maximum input level for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 7.5F Adjacent Channel Selectivity (ACS) for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 7.6.1F In-band blocking for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 7.6.2F Out-of-band blocking for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 7.7F Spurious response for UE category NB1
WI-259 RF NB-IoT 3GPP TS 36.521-1 7.8.1F Wide band Intermodulation for UE category NB1

► Specific Field Trials (GCF) requirements based on GSMA specs: not yet

Slide 36 © 2016 AT4 wireless - a DEKRA company

 GCF, PTCRB, GSMA
► GCF Work Items “Machine Type Communications (MTC)”
► Not explicitly related with IoT
For mobile networks to be competitive for
mass machine-type applications, it is important
to optimise their support for machine-type
communications. The current mobile networks
are optimally designed for Human-to-Human
communications, but are less optimal for
machine-to-machine, machine-to-human, or
human-to-machine applications. It is also
important to enable network operators to offer
machine-type communication services at a low
cost level, to match the expectations of mass-
market machine-type services and
applications.
Slide 37 © 2016 AT4 wireless - a DEKRA company
Feature
Extended back-off timers
Minimum Periodic search timer
Attach with IMSI
Per-device timers
E-UTRA Comments
X Extended back -of f timer values that the
network can include when rejecting MM or SM
messages that are sent by UEs that have
previously indicated that they are configured
for Low Access Priority.
X This timer allows extended values for th e timer
that is used to control when a UE shall attempt
to access the HPLMN or an EHPLMN or
higher priority PLMN. It shall be used if it is
larger than the value stored on the SIM (in
EF HPPLMN) or the default value.
X A UE can be conf igured to, when registering
with a new mobile network, present its IMSI
rather than a temporary identity. This is used
to optimize PLMN change as the need to reject
the RA update, and to request the IMSI
following the subsequent Attach with P -TMSI,
is avoi ded.
X The network can allocate a long periodic TAU
timer to a UE that has previously indicated that
it is configured for Low Access Pri ority. A long
periodic RAU timer is likely to slow down the
rate at which an UE detects a network failure
and thus it slows down the rate of movement
of UEs from a failed network to other local
competing networks
 Adoption

Tier-1 operator in Asia

 Planned certification of modules intended for IoT during 2016
 Category 1
 Category 1 & 4
 Interested in other technologies such as SigFox and LoRa

Tier-1 operator in America

 Planned support of PSM: Q4’2016
 Category 1: already supported – module certification expected Q2’2016
 Category 0: not in the roadmap
 Category M1: partial support expected Q4’2016 – module certification expected
Q2’2017 – full availability expected Q4’2017
 Category NB1: partial support expected Q4’2016 – module certification expected
Q3’2017 – full availability expected 2018

Slide 38 © 2016 AT4 wireless - a DEKRA company

 Adoption
NB-IoT Forum
 China Mobile, China Unicom, Etisalat, LG U+, KDDI,
kt, Telecom Italia, Telefonica, Telekom, Verizon,
Vodafone

LoRa
 Bouygues, KPN, SK Telecom, Swisscom, du, Orange
SigFox
 Coverage in Europe
 Technical research in other areas, e.g. LATAM
 Operators in LATAM
 Brazil: WND
 Colombia: PHAXSI
 Mexico: IotNet Mexico

Slide 39 © 2016 AT4 wireless - a DEKRA company

 Adoption
NB-IoT “Battle” in Europe

Slide 40 © 2016 AT4 wireless - a DEKRA company

 Testing @ AT4
Laboratory Testing (Simulator) Roadmap

Category 1 Category M1
available available*

Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1
2016 2016 2016 2017 2017 2017 2017 2018

Category
Category 0
NB1
available*
available*

Feedback from providers:

Industry has skip Cat. 0 to prioritize Cat. M1 and NB1 * Investment required
Slide 41 © 2016 AT4 wireless - a DEKRA company
Contact AT4 wireless
Spain USA Taiwan
AT4 wireless, S.A. (HQ) AT4 wireless, Inc. AT4 wireless, Inc.
Parque Tecnologico de Andalucia 520B Huntmar Park Drive 16F-7, Nr. 266, Sec. 1,
C/ Severo Ochoa, 2 & 6 Herndon – Virginia 20170 - USA Wen Hua 2nd Road, Linkou Township
29590 Malaga - Spain Tel. +1 703 657 2000 Taipei County. Taiwan
Tel. +34 952 61 91 00 Fax. +1 703 870 7560 Tel. +886 2 7705 3300
Fax. +34 952 61 91 13 Fax. +886 2 7705 3301
San Diego Office infoTaiwan@at4wireless.com
Sevilla Office WaterGarden Business Center
C/ Isaac Newton, s/n 5755 Oberlin Dr#303 - CA92121
San Diego – California - USA
Japan
Centro de Empresas
Pabellon de Italia. 3rd floor Tel. +1 540 425 1215 Japan Authorized Test Laboratory
Isla de la Cartuja infoUSA@at4wireless.com (Partnership with Toyo Corporation)
41092 Seville - Spain 1-6, Yaesu 1-chome, Chuo-Ku
Tel. +34 954 46 00 09 Tokyo, 103-8284
Fax. +34 954 46 00 09 Japan
Tel. +81 3 3245 1250
Madrid Office hatakeyamak@toyo.co.jp
Ave. Felipe II, 15. 1st floor
28009 Madrid - Spain
Tel. +34 914 35 88 06 Chile
Fax. 34 914 35 64 23
AT4 wireless, Ltd.
info@at4wireless.com
Rosario Sur 91, 9th floor
Las Condes, Santiago. Chile
Tel. +56 2 57 78000
infoLATAM@at4wireless.com
www.at4wireless.com

Slide 42 © 2016 AT4 wireless - a DEKRA company

Thank you!

Internet of Things Seminar

Slide 43 © 2016 AT4 wireless - a DEKRA company