Machine Type Communications: 3GPP Standards Perspective


Published on

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Machine Type Communications: 3GPP Standards Perspective

  1. 1. 3GPP Standards PerspectiveNadeem AkhtarCentre of Excellence in Wireless Technology
  2. 2.  Overview Technical Challenges 3GPP M2M Architecture Features and Enhancements All rights reserved © CEWiT 2 03-12-2012
  3. 3.  Work on M2M standards is currently ongoing in several standardization bodies including 3GPP 3GPP specifies standards for 2G, 3G and 4G wireless communication technologies 3GPP is also working on specifications for deploying M2M services over 2G/3G/4G networks ◦ 3GPP prefers to call it Machine-Type Communication (MTC) All rights reserved © CEWiT 3 03-12-2012
  4. 4. Source: ETSIAll rights reserved © CEWiT 4 03-12-2012
  5. 5.  Current mobile networks were designed for human- to-human and human-to-machine interactions ◦ Telephony ◦ SMS/MMS ◦ Multimedia download and streaming M2M networks are characterised by ◦ Communication that involves little or no human interaction ◦ Large number of devices ◦ Periodic or intermittent network access ◦ Small amount of data per ‘session’ All rights reserved © CEWiT 5 03-12-2012
  6. 6. Device/Service System Requirement CharacteristicsLow Mobility Simplification of mobility control proceduresTime Controlled Enable communication at specific times onlyTime Tolerant Low priority while allocating transmission resourcesSmall Data Reduction in control signaling and the number ofTransmissions concurrent/active network connectionsPacket Switched Data Access to services with or without a mobile numberOnlyMobile Originated Only Reduction in frequency of mobility controlDevice Triggering Transmission of trigger from network to control deviceDevice Grouping Aggregate a set of devices to optimize control All rights reserved © CEWiT 6 03-12-2012
  7. 7. Source: TNOAll rights reserved © CEWiT 7 03-12-2012
  8. 8.  The following features and enhancements have been identified by 3GPP for Machine Type Communications ◦ Overload/Congestion Control ◦ Identifiers and Addressing ◦ Triggering and Remote Management ◦ Subscription Control and Charging ◦ Security ◦ Lower Device Cost All rights reserved © CEWiT 8 03-12-2012
  9. 9. MTCMTC App MTC App Operator Interworking MTC Server MTC Device Network Function All rights reserved © CEWiT 9 03-12-2012
  10. 10.  Direct ◦ The MTC Application communicates with the MTC device directly as an OTT application on mobile network Indirect ◦ The MTC Application makes use of an MTC Server provided by the operator ◦ The interface between the MTC Server and the MTC application remains still out of the scope of 3GPP ◦ The communication between the MTC server and the mobile network becomes internal to the PLMN All rights reserved © CEWiT 10 03-12-2012
  11. 11.  Service Provider Controlled ◦ The MTC Application makes use of an MTC Server, provided by a third party Service Provider ◦ The interface between the MTC server and the MTC application is totally out of the scope of 3GPP ◦ The MTC server communicates with the 3GPP network by means of an interface or set of interfaces All rights reserved © CEWiT 11 03-12-2012
  12. 12. MTC App MTC App MTC App MTC Server MTC Server Operator Operator Operator Network Network Network BMTC App MTC App MTC App MTC App MTC App MTC App MTC Device MTC Device MTC Device All rights reserved © CEWiT 12 03-12-2012
  13. 13. Legacy SMS SMS-SC / IP SMS IP-SM-GW HLR / HSS CDF/ CGF Gr/S6 a/ Rf/Ga T4 MTCsms S6 m service provider controlled S 6d operator controlled SGSN / MME MTC-IWF T5a/T5b MTCsp MTC RAN GGSN / MTC 1 MTC MTCApplication UE S-GW+P-GW Server Application User Gn/Gp/S1-U Gi/SGi API Um / Uu / - LTE Uu 2 Indirect Model 1 Gi/SGi Control plane Direct Model 2 User plane 3GPP Hybrid Model 1 + 2 Boundary All rights reserved © CEWiT 13 03-12-2012
  14. 14.  MTC-related enhancements defined in 3GPP Rel. 10 and Rel. 11 specifications to address overload 3G/4G networks ◦ ‘Delay-tolerant’ indication sent by MTC device to RAN at setup ◦ RAN can reject/release “delay tolerant” connections with “extended wait timer” (up to 30min) ◦ CN can indicate “overload” to RAN to limit delay-tolerant traffic 2G networks ◦ CN can notify GERAN of a CN overload situation ◦ An implicit reject mechanism can be used by the network to reject all devices configured for low priority access ◦ MTC-specific broadcast mechanism for access barring All rights reserved © CEWiT 14 03-12-2012
  15. 15.  Release 11 of 3GPP will be frozen by March 2013 In parallel, work on Rel. 12 has already started ◦ MTC work will continue in Release 12 also Study on low-cost MTC devices for LTE is currently ongoing Work towards specifications for such devices is expected to start next year All rights reserved © CEWiT 15 03-12-2012
  16. 16. All rights reserved © CEWiT 16 03-12-2012
  17. 17. rights reserved © CEWiT 17 03-12-2012