m2m applications and 3gpp cellular networks · 2016. 5. 17. · rel-12: study of power saving for...
TRANSCRIPT
M2M applications and 3GPP cellular networks
Genadi VelevNEC Laboratories Europe
Page 2 © NEC Corporation 2014
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 3 © NEC Corporation 2014
▌ Traditional applications Voice, multimedia, large data Highly mobile devices No strict requirements for chipset
price and battery life
Challenges for 3GPP cellular networks
▌ M2M application chatacteristics Business: low ARPU Device requirements: low price, long
battery life Data chatacteristics: small data,
periodic, (in)frequent
Page 4 © NEC Corporation 2014
▌ Why 3GPP cellular network as transport for M2M applications?
3GPPCore
End-to-end architecture
GPRS/UTRAN/LTE
BTS/(e)NB
M2Mlocal
network
M2M capabilityServer
(IN-CSE)
M2M App
3GPP transport network
3GPP to meet M2M device requirements
3GPP enables access to/from M2M providers
M2M App
M2M App
M2M App
3GPP mainscope
(AE)3GPP UE(M2M GW)(MN-CSE)
3GPP offers to 3rd parties: C-plane access (network APIs) IP bearer service SMS service
Deployment aspect: Global, wireless reachability Operators deploy M2M platforms SoC allows embedded modem
(<5$) into sensors/meters
NetworkAPIs
IP access
SMS
3GPP UEs(single devices)
(ASN-CSE)
Page 5 © NEC Corporation 2014
3GPP System Architecture evolution (1/3)
▌ Release 10 (NIMTC) Started with a dozen of features.... Congestion/overload control in the network
• low access priority devices• ... later dual priority devices• Extended Access Class Barring (EAB)
▌ Release 11 (SIMTC) 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
▌ Release 12 UE Power Consumption Optimizations (UEPCOP)
• Power saving mode (PSM): UE not reachable during PSM state. Small Data and Device Triggering (SDDTE)
• Core Network assisted eNB parameters for small data transfer
=> Release 13 ongoing (following slides)
2011
2012
2013
2014
Rel
-10
Rel
-11
Rel
-12
Rel
-13
2010
Page 6 © NEC Corporation 2014
3GPP System Architecture evolution (2/3)
S6n
Services Capability
Server(SCS)
Gi/SGi
TspControl plane
User plane
Indirect Model
Direct Model
Hybrid Model
GGSN/P-GW
MTC-IWF
SMS-SC/GMSC/IWMSC
2
1
1
T4
Rf/Ga S6m
T5c
Um /Uu /
LTE-Uu
MTC UE Application
MME
HPLMN
VPLMN
Gi/SGi
SGSN
S -GW
UE
MSC
RAN
T5bT5a
CDF/CGF
Tsms
Application Server(AS)
1
Application Server(AS)
2
IP-SM-GW
HSS
2+
SME
MTC AAA
Release 11(Device Triggering)
Page 7 © NEC Corporation 2014
3GPP System Architecture evolution (3/3)
Service Capability Exposure Function
Application
API 1
Application
Application
API 2 API 3 API n...OMA/GSMA/
other SDOs
HSS PCRF MTC-IWF
NetworkEntity
3GPP
...
MME/SGSN
Sh Rx Tx Tsp 3GPP Interface
SMS-SC/GSMSC/IWMSC
T4/Tsms
ISC
S-CSCF
Release 13(service exposure architecture)
Release 11(Device Triggering)
S6n
Services Capability
Server(SCS)
Gi/SGi
TspControl plane
User plane
Indirect Model
Direct Model
Hybrid Model
GGSN/P-GW
MTC-IWF
SMS-SC/GMSC/IWMSC
2
1
1
T4
Rf/Ga S6m
T5c
Um /Uu /
LTE-Uu
MTC UE Application
MME
HPLMN
VPLMN
Gi/SGi
SGSN
S -GW
UE
MSC
RAN
T5bT5a
CDF/CGF
Tsms
Application Server(AS)
1
Application Server(AS)
2
IP -SM-GW
HSS
2+
SME
MTC AAA
Page 8 © NEC Corporation 2014
3GPP System Architecture: Release 13
▌ Architecture Enhancements for Service Capability Exposure (AESE) Architecture agreed Exposing network services to 3rd party
▌ 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)
3GPP Core
communicationwindow
traffic pattern,mobility pattern
negotiateQoS,
priorities
(1)
(3)
(2)MONTE
GROUPE
Page 9 © NEC Corporation 2014
3GPP Radio Access (RAN/GERAN)
▌ RAN1/2 (UTRAN, LTE) Release 11
• Implementing SA specs on congestion/overload control• Study on Low Cost UE
(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”)
Release 13• RAN enhancements for small data transmission in LTE
▌ GERAN (GPRS) Rel-12: Study of Power Saving for MTC Devices (uPoD) Rel-13: Support for Ultra Low Complexity
and Low Throughput IoT (Cellular IoT)• Data rate >= 160 bps• Battery lifetime > 10 years• Massive number of devices (40 per household)• Optionally non backward compatibility
2G is the legacy M2M business of 3GPP operators
Rel
-10
Rel
-11
Rel
-12
Rel
-13
LTE is considered for M2M business
2011
2012
2013
2014
2010
Page 10 © NEC Corporation 2014
▌ 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).
Towards 5G
Page 11 © NEC Corporation 2014
▌ 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)
3GPPCore
Summary
GPRS/UTRAN/LTE
BTS/(e)NB
M2M capability and/orApp Server
3GPP transport network
3GPP targets M2M device requirements
3GPP enables access to/from M2M providers
M2M devices
Network internal oprimizations for M2M
NetworkAPIs
IP access
SMS
Page 12 © NEC Corporation 2014