3GPP Enhancements for Machine Type Communications Overview


Published on

1 Comment
  • 'After being in relationship with Wilson for seven years,he broke up with me, I did everything possible to bring him back but all was in vain, I wanted him back so much because of the love I have for him, I begged him with everything, I made promises but he refused. I explained my problem to someone online and she suggested that I should contact a spell caster that could help me cast a spell to bring him back but I am the type that don't believed in spell, I had no choice than to try it, I meant a spell caster called Dr Zuma zuk and I email him, and he told me there was no problem that everything will be okay before three days, that my ex will return to me before three days, he cast the spell and surprisingly in the second day, it was around 4pm. My ex called me, I was so surprised, I answered the call and all he said was that he was so sorry for everything that happened, that he wanted me to return to him, that he loves me so much. I was so happy and went to him, that was how we started living together happily again. Since then, I have made promise that anybody I know that have a relationship problem, I would be of help to such person by referring him or her to the only real and powerful spell caster who helped me with my own problem and who is different from all the fake ones out there. Anybody could need the help of the spell caster, his email: spiritualherbalisthealing@gmail.com or call him +2349055637784 you can email him if you need his assistance in your relationship or anything. CONTACT HIM NOW FOR SOLUTION TO ALL YOUR PROBLEMS'
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

3GPP Enhancements for Machine Type Communications Overview

  1. 1. IEEE WoWMoM 2012 Panel“3GPP Enhancements for Machine Type Communications Overview“ Presenter: Yenamandra S Rao Contributors: Francesco Pica and Dilip Krishnaswamy Qualcomm
  2. 2. 3GPP Machine Type Communications• Outline – 3GPP MTC standards – 3G PP Basic MTC architecture – MTC Characteristics – MTC 3GPP Release 10 features • RAN and CN Congestion/Overload protection – MTC 3GPP Release Work Items • MTC Low Cost Model – 3GPP New MTC Architecture • Services Capability Layer • MTC Inter Working Function (IWF)
  3. 3. Machine Type Communications (MTC) Spec Specifications associated with or affected by MTC work 22.011 Service accessibility 22.368 Service requirements for Machine-Type Communications (MTC); Stage 1• M2M is recognized as a key segment in 23.008 23.012 Organization of subscriber data Location management procedures future cellular mobile packet data 23.060 23.122 General Packet Radio Service (GPRS); Service description; Stage 2 Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode networks 23.203 23.401 Policy and charging control architecture General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access• Initial 3GPP efforts have focused on the 23.402 23.888 Architecture enhancements for non-3GPP accesses System improvements for Machine-Type Communications (MTC) ability to differentiate MTC -type 24.008 24.301 Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 devices 24.368 25.331 Non-Access Stratum (NAS) configuration Management Object (MO) Radio Resource Control (RRC); Protocol specification 29.002 – This allows the operator to selectively Mobile Application Part (MAP) specification General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors 29.018 Location Register (VLR); Gs interface layer 3 specification handle such devices in 29.060 General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface congestion/overload situations 29.118 Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification • Low priority indicator has been added to 29.274 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 the relevant UE-network procedures 29.275 Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols; Stage 3 29.282 Mobile IPv6 vendor specific option format and usage within 3GPP • Overload and Congestion control is done 31.102 Characteristics of the Universal Subscriber Identity Module (USIM) application 33.868 on both core network and radio access 36.331 Security aspects of Machine-Type Communications Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification network based on this indicator 37.868 RAN Improvements for Machine-type Communications 43.868 GERAN Improvements for Machine-type Communications 44.018 Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System 44.060 (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol 45.002 Multiplexing and multiple access on the radio path
  4. 4. 3GPP MTC Architecture• source 3GPP (http://www.3gpp.org) HLR / Legacy SMS SMS-SC HSS IP-SM-GW Indirect model – IP SMS service provider controlled MTCsms Indirect model – Gr/S6a operator controlled SGSN / Internal Proxy MME interfaces (TBD) MTCsp (TBD) M2M RAN GGSN / MTC Server M2MApplication UE PGW / Application PDG MTCi API Um / MTC Uu / User LTE-Uu Gi/SGi Direct model Control planUser 3GPP plane Boundary
  5. 5. 3GPP Rel-10 RAN features summaryTwo main features addressing network overload:• Core Network overload control – UTRAN, E-UTRAN and GERAN• RAN overload control – GERAN-only (EAB - Extended Access Barring)RAN capabilities standardized in Rel-10 – Ability to configure MTC devices as (access) delay tolerant UEs • “intended for use with MTC Devices that can delay their data transfer” – UTRAN and E-UTRAN • ‘Delay-tolerant’ indication sent by low-priority access UEs to RAN at RRC setup • ‘Extended wait time’ (up to 30min) sent by the RAN to low-priority access UEs – GERAN • Core Network Overload: An Implicit reject mechanism (& reject timer up to 200 sec) is defined for the BSC to reject all devices configured for low priority access • RAN overload: EAB, a MTC-specific broadcast mechanism for access barring
  6. 6. CN Overload control in (E)UTRAN: OverviewNew signaling has been introduced in (E)UTRAN for CN overload control– Core Network can indicate “overload” to RAN (not per UE), to limit Delay Tolerant traffic Overload RNC/NB CN/EPC New Indication: Delay Tolerant traffic limited)– UE can indicate “delay tolerant” at Radio connection setup RRC Connection Request UE RNC/NB CN/EPC (new establishment cause = Delay Tolerant Access)– RAN can reject/release “delay tolerant” connections with “extended wait timer” (eWT) RRC Connection Reject/Release (or Signaling Connection Release) UE RNC/NB CN/EPC (new Extended Wait Time)
  7. 7. CN Overload control in GERAN: Overview• CN can notify GERAN of a CN overload situation (as for (E)UTRAN) Overload BSS CN New Indication: Delay Tolerant traffic limited)• In GERAN, there is no explicit UE indication and RAN reject – An implicit reject mechanism can be used by the network to reject all devices configured for low priority access. • A mobile station configured for “low access priority” that fails to receive a response to its access attempt but determines the BSS has enabled the implicit reject feature will abort the access procedure and start an implicit reject timer. • While an implicit reject timer is running in a mobile station it shall consider itself as being unable to make further system access attempts
  8. 8. GERAN RAN Overload ControlExtended Access Barring (EAB)• Extends legacy Access Control Barring (ACB), which can bar ALL UEs in a cells• In Rel-10, UEs configured for EAB are also Delay Tolerant (and vice versa).• In congestion, GERAN can restrict access from UEs configured for EAB only• A UE configured for EAB shall use its allocated Access Class(s) and sub-category when evaluating the EAB information that is broadcast by the network, in order to determine if its access to the network is barred
  9. 9. Extended Access Barring (EAB)EAB requirements/functions for GERAN Rel-10• EAB applies to Mobile Originated (MO) calls only, except emergency calls• The UE is configured for EAB by the HPLMN. EAB shall be applicable regardless of whether the UE is in a Home or a Visited PLMN• If a UE that is configured for EAB is a member of an Access Class 11-15 permitted by the network, then the UE shall ignore EAB AC 11: Reserved for the network operator; AC 12: Security Services (Police, Surveillance) Special Access Classes AC 13: Public Services (Electricity,Distribution,etc); AC 14: Emergency Services (SIM based) not subject to EAB AC 15: Reserved for the staff of the operator (eg. to on-site maintenance technicians)• EAB information shall include barring information for Access Classes 0-9, plus the differentiation of the following 3 sub-categories – A: The EAB Authorization mask is applicable to all mobile stations configured for EAB. – B: The EAB Authorization mask is only applicable to mobile stations configured for EAB and registered neither in their HPLMN nor in a PLMN that is equivalent to it – C: The EAB Authorization mask is only applicable to mobile stations configured for EAB and registered neither in the PLMN listed as most preferred PLMN of the country where the UE is roaming in the operator-defined PLMN selector list on the SIM/USIM, nor in their HPLMN nor in an PLMN that is equivalent to it 9
  10. 10. 3GPP MTC Rel-11 features• Few parallel Work/Study Items are ongoing in Rel-11 (still open) – Two study Items on RAN improvements for Machine-Type Communications were started in 4Q ‘09 for GERAN and (E)UTRAN, as follow-up from Rel-10 – One large umbrella WI, System Improvements to Machine-Type Communications (SIMTC), started in May 2010, including • Many System/Core Network features and enhancements • One Work Item, common for UTRAN and EUTRAN, on RAN overload control – One study item on Study on Provision of low-cost MTC UEs based on LTE (FS_LC_MTC_LTE) was started in Sept. 2011• Motivations – Continue to enhance MTC related system/UE performance • Specific motivations for different SI/WIs are described
  11. 11. 3GPP Rel-11 RAN MTC enhancements• EAB (Extended Access Barring) for (E)UTRAN – Providing RAN (and CN) overload control – Includes overload control for shared RANs• Low cost MTC for LTE – Enabling “low cost” LTE M2M devices in the future• Further enhancements to RAN overload control – Under study for both GERAN and (E)UTRAN – Details can be found in related 3GPP TRs: • TR 37.868: Study on RAN Improvements for Machine-type Communications • TR 43.868: GERAN Improvements for Machine-type Communications
  12. 12. 3GPP Rel-11 Low Cost LTE MTC• Study Item – Target is Rel-12• Proposals in 3 main areas: Radio (RF), Baseband, Operation – Five techniques are discussed in RAN1 for cost reduction: • Reduction of maximum bandwidth • Single receiver RF chain • Reduction of peak rate • Reduction of transmit power • Half duplex operation
  13. 13. 3GPP MTC New Architecture IP-SM-GW SMS Tsms SC/GMSC/ SME IWMSC CDF/ HSS T4 CGF S6m Rf/Ga MTC-IWF Tsp Control plane User plane Services Application 1 Capability Server Server Gi/SGi T5c GGSN/ P-GW Application 2 T5b Server T5a Gi/SGi HPLMN VPLMN MSC Indirect Model 1 MME MTC UE Direct Model 2 Application UE RAN SGSN Hybrid Model 1 + 2 S-GW Um / Uu / LTE-Uu13
  14. 14. 3GPP Service Capability Server (SCS) • The SCS offers capabilities for use IP-SM-GW SMS SC/GMSC/ Tsms SME by one or more MTC Applications. – SCS is a primarily a service platform IWMSC – SCS not defined in 3GPP CDF/ HSS T4 CGF S6m Rf/Ga – E.g., Platform standardized by ETSI MTC-IWF Tsp Control plane User plane Services Capability Server Application Server 1 • SCS is controlled by the operator T5c GGSN/ Gi/SGi of the HPLMN or by a MTC P-GW T5b T5a Gi/SGi Application Server 2 Service ProviderHPLMNVPLMN • The API between SCS and the MSC MTC UE MME Indirect Model Direct Model 1 2 MTC Application(s) is outside the UE RAN scope of 3GPP specifications Application SGSN Hybrid Model 1 + 2 S-GW Um / Uu / LTE-Uu
  15. 15. 3GPP MTC Interworking Function (MTC-IWF) • MTC-IWF is controlled by HPLMN IP-SM-GW SMS SC/GMSC/ Tsms SME operator • The MTC-IWF is in the HPLMN IWMSC CDF/ HSS T4 • SCS communicates with MTC-IWF CGF S6m Rf/Ga Control plane MTC-IWF Tsp through Tsp interface Services Application 1 • MTC-IWF interfaces with other User plane Capability Server Server Gi/SGi T5c T5b GGSN/ P-GW Application Server 2 3GPP entities for various MTC services T5a Gi/SGiHPLMNVPLMN MSC – Example for device trigger Indirect Model 1 MTC UE MME Direct Model 2 submission via SMS Application UE RAN SGSN Hybrid Model 1 + 2 S-GW Um / Uu / LTE-Uu