1 | 3GPP2 TSG-X Discussion | December 2010 3GPP2 X50-20101206-015R1 TITLE: TITLE: M2M Deployment Scenarios for 3GPP2SOURCE Mike Dolan, Alcatel-Lucent,

Slides:



Advertisements
Similar presentations
The contributors grant a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material.
Advertisements

SOURCE:Alcatel-Lucent CONTACT: Nancy Mudit Satish.
Source Avi Lior, Bridgewater Jun Wang and George Cherian, Qualcomm Incorporated Dec 07, 2009 Page 1 IPv4 Exhaustion and IPv4-IPv6 Transition in 3GPP2 Notice.
1 DSMIP6 Support QUALCOMM Inc. Jun Wang, George Cherian, Masa Shirota Notice.
IP Connectivity for E911 in HRPD/PDS Networks Page 1 IP Connectivity for Emergency Calls in HRPD/PDS Networks 3GPP2 Meeting, 1/07 IP Connectivity for Emergency.
XHRPD Example Scenario for MSS Masa Shirota Qualcomm Inc. July 15, GPP2 Dalian Meeting Recommendation: FYI Notice QUALCOMM Incorporated grants a.
3GPP2 A r0 3GPP2 C xxxr0 TSG-A WG3 and TSG-C WG2 Title: HRPD Redirect on EPC Unavailable Source: Mike DolanAlcatel-Lucent Dave.
HRPD Femto Local IP Access: Overview Peerapol Tinnakornsrisuphap Qualcomm October 27 th, GPP2 Seoul,
1 Title: TDF support in cdma2000 1x and HRPD Networks Sources: China Telecom, ZTE, Huawei Contact: CT: Heng Nie ( ), Congjie Mao(
May 14, 2007 Violeta Cakulev, Mike Dolan, Frank Alfano, Nancy Lee - Alcatel-Lucent ABSTRACT: This contribution discusses the benefits on several features.
ABSTRACT: This contribution proposes the HRPD-WiMAX handoff solution. TITLE: HRPD-WiMAX Handoff TSG-A WG4 RECOMMENDATION: Review and Adopt Samsung Electronics.
© Alcatel-Lucent | M2M Numbering | April 12, GPP2 M2M TITLE Numbering in 3GPP2 for M2MSOURCE Mike Dolan, Alcatel-Lucent, Mike.
3GPP2 Femto Cell Workshop
3GPP2 X xxx Title: SIP6 access and MIP6 Access Differentiation Sources: ZTE Contact: Rajesh Bhalla
The contributing companies grant a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable.
ABSTRACT: This contribution offers some suggestions for the support of Femto Devices in 3GPP2 standards. TITLE: Femto Device Support TSG-A WG4 RECOMMENDATION:
Broadcast/Multicast Priority List JUNHYUK SONG SAMSUNG Incorporated grants a free, irrevocable license to 3GPP2 and its Organization Partners to incorporate.
Source Avi Lior, Bridgewater Jun Wang and George Cherian, Qualcomm Incorporated Dec 11, 2009 Page 1 IPv4 Exhaustion and IPv4-IPv6 Transition in 3GPP2 The.
QUALCOMM PROPRIETARY 3GPP2 Network Evolution Architecture Dec. 04, 2006 Lucent Technologies Nortel Networks Qualcomm Inc. Hitachi, Ltd Huawei Technologies.
HUAWEI TECHNOLOGIES CO., LTD. Slide title :40-47pt Slide subtitle :26-30pt Color::white Corporate Font : FrutigerNext LT Medium Font to.
1 Flow Mobility Support QUALCOMM Inc. George Cherian, Jun Wang, Masa Shirota
X xxx China Telecom Requirements on Accounting at HA/LMA Title: Accounting at HA/LMA for cdma2000 (Work Item # 3GPP ) Sources: China Telecom.
Proposed Solution for Device Binding 3GPP2 TSG-S WG4 S Source: Qualcomm Incorporated Contact(s): Anand Palanigounder,
May 12, 2008 Alcatel Lucent, Cisco, Motorola, Nortel, Verizon ABSTRACT: Proposed is additional key hierarchy and derivation for EPS access over eHRPD.
16 June Lucent Technologies grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable.
X xxx ZTE Discussion on cdma2000 Charging with PCC Title: Discussion on PCC Charging for cdma2000 1x and HRPD Sources: China Telecom, ZTE Contact:
5 November Overview of Proposed Femtocell Architecture Alternatives presented at the 3GPP2 Femto Workshop Airvana 5 November 2007 cdma2000® is the.
1 Authentication and User Profile April 24, 2007 Jun Wang QUALCOMM Inc. Notice Contributors grant a free, irrevocable license to 3GPP2 and its Organization.
X xxx ZTE Discussion on cdma2000 Charging with PCC Title: Discussion on handover indicator transfer in S2a Sources: China Telecom, Huawei, Alcatel-Lucent.
Title: Type: Arial Bold Size : 32-36pt Color : The theme blue Subtitle: Type : Arial Size : 24pt Color: The theme gray 1 TSG-AC WG2 HRPD/eHRPD enhancements.
3GPP2 SX r0 TSG-SX WG3 - PDS Title: Overview of the 3GPP TFT change and Possible Solutions Source: TSG-SX WG3 Chair and Vice Chair Abstract:
ABSTRACT: This contribution introduces the inter-RAT fast handover solution. TITLE: Inter-Radio Access Technology Fast Handover TSG-A WG4 RECOMMENDATION:
1 | L2-Tunnel based – Inter-tech. HO | October 29, 2007 Title: An L2-Tunnel based method for UMB-HRPD Inter-Technology handoff Source: Alcatel-Lucent,
SOURCE: Satish Kanugovi Subramanian Vasudevan Orlett Pearson
TSG-A WG3 Title: Possible solution for HRPD-LTE SON Source: Yuanfang Yu, Xiaowu Zhao, Ting Lu, Yonggang Fang Abstract: This contribution provides a possible.
ABSTRACT: This contribution proposes the HRPD-WiMAX handoff solution. TITLE: HRPD-WiMAX Handoff TSG-A WG4 RECOMMENDATION: Review and Adopt Samsung Electronics.
Supporting Local Breakout in HRPD Femto Peerapol Tinnakornsrisuphap Qualcomm Doug Knisely
August 25, 2008 Alcatel Lucent ABSTRACT: 1x System Reliability is important in the face of major events, such as an earthquake. There are several ways.
3GPP2 Network Evolution: UMB->HRPD Handoff October 16, 2007 Qualcomm Inc. Contact: Jun Wang Notice Contributors grant a free, irrevocable license to 3GPP2.
Remote access to Local IP network via Femto Peerapol Tinnakornsrisuphap Anand Palanigounder
3GPP2 TSG-C SWG1.4 TITLE: Clarifications for IOTA Proposal SOURCE: Nick J. Mazzarella 1960 Lucent Lane Naperville, IL (630)
X xxx ZTE Discussion on cdma2000 Charging with PCC Title: Inter-RAT RAN information management protocol Stack Sources: NSN Contact: Scott Marin,
3GPP2 X xxx Title: Subscriber QoS Profile Support in eHRPD System Sources: China Telecom, ZTE Contact: CT: Peirong Li Wenyi.
Comment to Limited Idle Mode Nortel Networksgrants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable.
1 | Tunneling Method – Inter-tech. HO | August 2007 Title: A Tunneling Method for Inter-Technology Handoff Source: Mike Dolan, Alcatel-Lucent,
August 2012 C2 – Company Confidential SOURCE: Jialin Zou, Satish Kanugovi, Orlett Pearson (Alcatel-Lucent)… satish.k
EHRPD-LTE Inter Technology Spectrum Optimization Source: Qualcomm Incorporated Contact: Jun Wang/George Cherian September 9, 2013 Notice ©2013. All rights.
M2M Enhancement for HRPD Rev C VIA Telecom grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable.
Tunneling Protocol Structures for UMB to HRPD Interworking Linhai He Peerapol Tinnakornsrisuphap
1 MAPSUP in eHRPD: Data forwarding Tunnel Sources: ZTE Contact: Bi YiFeng Rajesh Bhalla
X xx CT+ZTE PCC for cdma2000 MS Init Call Flows 1 1 Title: PCC for cdma2000 – MS-Init Call Flow Example Sources: CTC, ZTE Contact: CHINA TELECOM.
Improved CDMA Mobile Hashing Lucent Technologies grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other.
1 MAPSUP in eHRPD Sources: ZTE Contact: Bi YiFeng Rajesh Bhalla ABSTRACT:
C Title: Next Steps for Femtocells Date: 03 December 2007 Source: Airvana, Alcatel-Lucent, Nortel Abstract:The contribution addresses.
Idle-State Data Buffering and Paging Framework June 04, 2007 Source companies grant a free, irrevocable license to 3GPP2 and its Organizational Partners.
1 3GPP2 A TITLE: TITLE: Energy Saving Mode Architecture ThoughtsSOURCE Scott Marin,
0 软交换应用的探讨 赵慧玲 2004 年 05 月 Dynamically Coverage Management By Caiqin Zhu(Catherine Zhu) China Telecom Apr © GPP2 China Telecom.
1 Subject:Draft Responses to BBF Comments re. cdma2000 MO Preview Date: 25 January 2010 Source: Doug Knisely TSG-X FMOAHG Co-chair, BBF Liaison Contact:
Adding LTE-1x CSFB IOS specification in 3GPP2 Sources: China Telecom, Contact: Li Wenyi ABSTRACT: This contribution is to analyze the.
Signaling Packet Routing for Layer 3 approach in UMB-HRPD/1x interworking KDDI Corporation, Tsunehiko Chiba, Osamu.
HUAWEI TECHNOLOGIES CO., LTD. HUAWEI TECHNOLOGIES Co., Ltd. Page 1 Zhiming Li 18 Feb Notice.
Benefits of eBS for UMB Qualcomm Inc. January 08, 2007 Notice Contributors grant a free, irrevocable license to 3GPP2 and its Organization Partners.
3GPP2 A r0 3GPP2 C xxxr0 TSG-A WG3 and TSG-C WG2 Title: M2M Congestion Control in the RAN Source: Mike Dolan Dave Rossetti Satish.
Clarifications on Work Split among TSG-X/A for 3GPP2 Network Evolution March 26, 2007 Airvana/Alcatel-Lucent/CTC/Fujitsu/ Hitachi/KDDI/NEC/Qualcomm/ZTE.
Inter-RAT Measurement Control Jungsoo Jung Samsung Electronics Samsung Electronics grants a free, irrevocable license to 3GPP2 and.
1 Lucent Technologies grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained.
August 2012 C2 – Company Confidential SOURCE: Jialin Zou, Satish Kanugovi, Orlett Pearson (Alcatel-Lucent)… satish.k
3GPP2 C r0 TSG-C SWG2.2 Title: Congestion Study of HRPD/eHRPD Networks Source: Alcatel-Lucent – Mike Dolan Abstract: This contribution provides.
Requirement for Proxy Mobile IP tunnel for AGW-eBS data tunnel Qualcomm, Inc. Contributors grant a free, irrevocable license to 3GPP2 and its Organization.
TSG-A WG4 TITLE: GRE L2TPv3 Comparison SOURCE:
Presentation transcript:

1 | 3GPP2 TSG-X Discussion | December GPP2 X R1 TITLE: TITLE: M2M Deployment Scenarios for 3GPP2SOURCE Mike Dolan, Alcatel-Lucent, Mike Dolan, Alcatel-Lucent, Orlett Pearson, Alcatel-Lucent, Betsy Covell, Alcatel-Lucent, (Omar Elloumi, Harish Viswanathan)ABSTRACT This contribution provides discussion points for IP addressing, deployment possibilities for IPv4/IPv6, 1x SMS and 1x Packet. RECOMMENDATION : Discuss and adopt in principle. © 2010 Alcatel-Lucent Alcatel-Lucent grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it may include all or portions of this contribution; and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contribution or the resulting Organizational Partner's standards publication. Alcatel- Lucent is also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner's standard which incorporates this contribution. This document has been prepared by Alcatel-Lucent to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on Alcatel-Lucent. Alcatel-Lucent specifically reserves the right to amend or modify the material contained herein and to any intellectual property of Alcatel-Lucent other than provided in the copyright statement above.

M2M Deployment Scenarios for 3GPP2 networks - Prioritization of 3GPP2 work December 2010

3 | 3GPP2 TSG-X Discussion | December 2010 Outline Reference from Possible Deployment Scenarios Pros and Cons of each Scenario Suggested way forward

4 | 3GPP2 TSG-X Discussion | December 2010 Reference from Source: 3GPP TR V1.0.0 ( ) Figure : IP address assignment when the MTC Server is owned by the MNO or by a M2M Application Provider using a specific dedicated APN Source: 3GPP TR V1.0.0 ( )

5 | 3GPP2 TSG-X Discussion | December 2010 TR- Discussion Points for IP Addressing NOTE:  Operators may have a choice of two solutions  IPv6  IPv4  Any choice the operator would make using NAT or application routing is an issue if the application puts in the IP address.  If address is embedded, and the address changed from A to B, then there is a possibility of applications failing.  If NAT or application level routing is used, then if the M2M application embeds IP addresses in the data being sent, there could be potential problems.

6 | 3GPP2 TSG-X Discussion | December 2010 M2M Deployment Possibilities We consider only mobile devices that fully support existing 3GPP2 specifications. 1. eHRPD based deployments supporting both IPv4 and IPv6 2. HRPD IPv4 based deployments 3. HRPD IPv6 based deployments 4. 1x SMS based deployments 5. 1x packet based deployments

7 | 3GPP2 TSG-X Discussion | December eHRPD based deployments supporting both IPv4 and IPv6  eHRPD attaches to the EPC, and so can participate in all of the M2M configurations supported by the EPC.  Multiple APNs, each with an IPv4 and an IPv6 address  Operator Policy via the PCRF  IP address assignment by the operator, or by the PDN  Requires at least basic EPC deployment  Supports multiple M2M clients on the same device attaching to separate M2M servers with private IP address spaces

8 | 3GPP2 TSG-X Discussion | December HRPD IPv4 based deployments M2M Device HA PDSN Pubic Internet Private IPv4 Address Space M2M Server A M2M Server B M2M Server C M2M Proxy Private IPv4 Address Space M2M Server X M2M Server P M2M Server Q 2a 2b 2c 2a – Public IPv4 address 2b – Private IPv4 address used to access all M2M servers 2c – Private IPv4 address used to access an M2M proxy that forwards M2M communications to M2M servers that could be in other address spaces.

9 | 3GPP2 TSG-X Discussion | December a. HRPD IPv4 based deployments – Public IPv4  The M2M device has a public IPv4 address and can thus reach all points in the internet.  Flexibility in M2M Server configuration and deployment  Use of large numbers of valuable IPv4 addresses  Some vulnerability to security attacks, depending on the quality of the security at the M2M application level

10 | 3GPP2 TSG-X Discussion | December b. HRPD IPv4 based deployments – Private IPv4 to All M2M Servers  The M2M device has a private IPv4 address that allows it to directly reach all M2M servers that it needs to communicate with.  The HA may be configured to recognize the device as being M2M and so assign it one of these private IPv4 addresses.  All M2M servers need to be configured into this same address space. If they are from separate M2M providers, this can lead to operational issues.  Use of large numbers of valuable public IPv4 addresses is avoided.  If the private IPv4 address space is managed totally within the operator’s controlled network, security issues are minimized.

11 | 3GPP2 TSG-X Discussion | December c. HRPD IPv4 based deployments – Private IPv4 access to M2M Proxy  Private IPv4 address used to access an M2M proxy that forwards M2M communications to M2M servers that could be in other address spaces.  M2M proxy provides a NAT-ing function.  The HA may be configured to recognize the device as being M2M and so assign it one of these private IPv4 addresses.  This configuration could be added to 2b to allow access to M2M servers both within and outside of the private IPv4 address space.  Benefit over 2b because all M2M servers do not need to be configured into this same address space.  Use of large numbers of valuable public IPv4 addresses is avoided.  If the private IPv4 address space is managed totally within the operator’s controlled network, security issues are minimized.  If the M2M applications embed IP addresses within their communications, this can cause problems because of NAT-ing.  If those communications are encrypted at the M2M application layer, the M2M proxy must become a forwarding application gateway that has separate encryptions toward the M2M Server, and toward the device.

12 | 3GPP2 TSG-X Discussion | December HRPD IPv6 based deployments  M2M device obtains an IPv6 address.  M2M Servers can be either in private address spaces, or in the public internet (3a and 3b – next slide).  IPv4/IPv6 address translation may be necessary to an IPv4 M2M server (3c – next slide).  Large IPv6 addresses may require compression over-the-air to avoid heavy impacts on the air interface.  Operator’s infrastructure must be prepared to handle IPv6.

13 | 3GPP2 TSG-X Discussion | December HRPD IPv6 based deployments M2M Device HA PDSN Pubic Internet Private Address Space M2M Server A M2M Server B M2M Server C v4-v6 NAT M2M Server X M2M Server P M2M Server Q 3a 3b 3c

14 | 3GPP2 TSG-X Discussion | December x SMS based deployments  Uses existing SMS techniques to deliver M2M communications over an SMS transport.  Well-known techniques that are easily built into M2M devices.  Impacts the 1x control/traffic channels as the number of M2M devices increases.  As 1x channels become increasingly important for carrying voice while high speed packet data is further deployed, it may be important to operators to keep 1x control channels free.

15 | 3GPP2 TSG-X Discussion | December x packet based deployments  Uses existing 1x packet data channels.  All 3 configurations for HRPD IPv4 apply equally in this scenario.  Impacts the 1x control/traffic channels as the number of M2M devices increases.  As 1x traffic channels become increasingly important for carrying voice while high speed packet data is further deployed, it may be important to operators to keep 1x traffic channels free.  Locking 1x traffic channel usage in for 10 years of M2M service may not be optimal in an operator’s spectrum plans.

16 | 3GPP2 TSG-X Discussion | December 2010 Suggested way forward  3GPP2 needs to focus its efforts on M2M in a way that will provide a step- wise approach.  First, support M2M devices that fully support the existing air interfaces.  Second, consider ways to mitigate congestion and loading problems caused by M2M.  Third, consider additional techniques that provide a significant performance improvement for a minimal network/air interface change.  3GPP2 needs to prioritize the scenarios to be supported as we consider the steps above. Operator preference of deployment scenarios would be helpful.