M2M Applications and 3GPP Cellular Networks

M2M applications and 3GPP cellular networks

Genadi Velev NEC Laboratories Europe A cellular operator: Can any of the 3GPP technologies (GSM, UMTS, LTE) be used to meet the M2M requirements?

 Low device price  Long battery life

NOTE: 3GPP uses Machine Type Communication (MTC) term beside M2M

Page 2 © NEC Corporation 2014 Challenges for 3GPP cellular networks

▌ Traditional applications ▌ M2M application chatacteristics  Voice, multimedia, large data  Business: low ARPU  Highly mobile devices  Device requirements: low price, long  No strict requirements for chipset battery life price and battery life  Data chatacteristics: small data, periodic, (in)frequent

Page 3 © NEC Corporation 2014 End-to-end architecture

▌ Why 3GPP cellular network as transport for M2M applications?

Deployment aspect: 3GPP offers to 3rd parties:  Global, wireless reachability  C-plane access (network APIs)  Operators deploy M2M platforms  IP bearer service  SoC allows embedded modem  SMS service (<5$) into sensors/meters

3GPP UEs (single devices) (ASN-CSE) Network APIs BTS/(e)NB M2M App

3GPP SMS M2M App GPRS/UTRAN/LTE Core M2M App M2M M2M capability M2M App IP access Server local (IN-CSE) (AE) network 3GPP UE 3GPP transport network (M2M GW) (MN-CSE)

3GPP main 3GPP to meet M2M device 3GPP enables access scope requirements to/from M2M providers

Page 4 © NEC Corporation 2014 3GPP System Architecture evolution (1/3)

2010 ▌ Release 10 (NIMTC)

 Started with a dozen of features.... Rel-10  Congestion/overload control in the network • low access priority devices 2011 • ... later dual priority devices • Extended Access Class Barring (EAB) Rel-11 ▌ Release 11 (SIMTC) 2012  Device Triggering TS23.682 (reachability from the M2M App server) • New network function MTC-IWF (Tsp interface to 3rd party)  SMS in MME (LTE only deployment)  MSISDN-less support 2013 ▌ Release 12

 UE Power Consumption Optimizations (UEPCOP) Rel-12 • Power saving mode (PSM): UE not reachable during PSM state.  Small Data and Device Triggering (SDDTE) 2014 • Core Network assisted eNB parameters for small data transfer

=> Release 13 ongoing (following slides) Rel-13

Page 5 © NEC Corporation 2014 3GPP System Architecture evolution (2/3)

Release 11

(Device Triggering) IP-SM-GW SMS-SC/ Tsms GMSC/ SME IWMSC

CDF/ HSS CGF T4

S6n MTC AAA Rf/Ga S6 m

MTC-IWF Tsp Control plane Services Application 1 User plane Capability Server Server (AS) (SCS ) Gi/SGi Application 2 T5c GGSN/ Server P-GW Gi/SGi (AS) T5b T5a HPLMN

VPLMN

MSC

MME MTC UE Application UE RAN Indirect Model 1 SGSN Direct Model 2 S-GW Hybrid Model 1 + 2 Um / Uu / LTE-Uu

Page 6 © NEC Corporation 2014 3GPP System Architecture evolution (3/3)

Release 11 Release 13 (Device Triggering) (service exposure architecture)

Application Application

Application

API 1 API 2 API 3 ... API n

OMA/ Service Capability Exposure Function GSMA/ other SDOs

IP-SM-GW SMS -SC/ Tsms GMSC/ SME IWMSC

CDF/ HSS CGF T4

S6n MTC AAA Rf/Ga S6 m

MTC-IWF Tsp 3GPP Control plane Services Application 1 User plane Capability Server Server (AS) (SCS ) Gi/SGi Application 2 T4/ 3GPP T5c GGSN/ Server Tsp ISC P-GW Sh Rx Tx Gi/SGi (AS) Tsms Interface T5b ... T5a HPLMN

VPLMN

MSC

MME MTC UE Application UE RAN Indirect Model 1 SGSN Direct Model 2 SMS-SC/ S-GW MME/ MTC- Network Hybrid Model 1 + 2 HSS PCRF GSMSC/ Um / S-CSCF Uu/ SGSN IWF Entity LTE-Uu IWMSC

Page 7 © NEC Corporation 2014 3GPP System Architecture: Release 13

▌ Architecture Enhancements for

Service Capability Exposure (AESE) negotiate  Architecture agreed traffic pattern, QoS, mobility pattern priorities communication  Exposing network services to 3rd party window 3GPP Core MONTE (1) (2)

(3) GROUPE ▌ Monitoring Enhancements (MONTE)  Configuring monitoring events in the network  Exposing network information to 3rd party for troubleshooting

▌ Group based Enhancements (GROUPE)  Group based messaging • Broadcast/multicast to a group (opt. in a geo area) • Group addressing and identifiers  Group based policing: QoS policies, congestion control

=> More M2M-related features are studied (HLCom, DECOR, eDRX)

LTE is considered for 2010 ▌ RAN1/2 (UTRAN, LTE) M2M business

 Release 11 Rel-10 • Implementing SA specs on congestion/overload control • Study on Low Cost UE 2011 (low data rate, 1 RX antenna, in-building coverage, half-duplex)  Release 12 • Specified a new Cat0 UE (result from Rel-11 “Low Cost UE”) Rel-11  Release 13 2012 • RAN enhancements for small data transmission in LTE

2G is the legacy M2M business of 3GPP operators ▌ GERAN (GPRS) 2013  Rel-12: Study of Power Saving for MTC Devices (uPoD)  Rel-13: Support for Ultra Low Complexity

and Low Throughput IoT (Cellular IoT) Rel-12 • Data rate >= 160 bps 2014 • Battery lifetime > 10 years • Massive number of devices (40 per household) • Optionally non backward compatibility Rel-13

▌ In the past (2G, 3G, 4G) The service requirements (SA1) did not consider M2M use cases => hence, later enhancements were needed

▌ In the future (5G, 2018~2020) SA1 to specify use cases based on M2M applications (e.g. ultra-fast network access, e.g. ~1ms latency for automated driving, industrial sensors, robots. Described in docs S1-144361, S1-144384).

▌ 3GPP standardizes M2M-specific features (since ~2010)  Network internal optimizations for M2M characteristics  Cheep and power efficient M2M devices (by RAN/GERAN WGs)  Unified access to/from M2M service providers (by SA WGs)

Network internal oprimizations for M2M

M2M devices Network BTS/(e)NB APIs

3GPP SMS GPRS/UTRAN/LTE Core M2M capability and/or IP access App Server 3GPP transport network

3GPP targets M2M device 3GPP enables access requirements to/from M2M providers