SOURCE: Satish Kanugovi (satish.k@alcatel-lucent.com), Subramanian Vasudevan (subramanian.vasudevan@alcatel-lucent.com),

Orlett Pearson (Orlett.Pearson@alcatel-lucent.com)

ABSTRACT: Support for HRPD air interface enhancements for M2M

TITLE: HRPD Enhancements for M2M

TSG-C

RECOMMENDATION: Discuss and adopt.

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 are 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.

Introduction

• Current networks are optimized for Human to Human communication, targeted for• High Bandwidth• Low Latency

• M2M represents a significant opportunity for the telecom service provider

• Standards enhancements are motivated by need to• better serve M2M traffic along with existing services• leverage the deployed 3G-1x and HRPD network infrastructure

Drivers for M2M enhancementsEfficiently Transport M2M Traffic

• Short Payloads• Signaling intensive• Huge Numbers

(Scalability)• Low Power• Low Cost• Bursty• Static & Mobile

DRIVERS SOLUTIONS

• Reduce overheads in initiating communications

• Network control of overload scenarios

• Substantial reduction in power consumption

Overview of 3G-1x Rev F EnhancementsM2M device Identification

Device to indicate its characteristic using General Extension Message (GEM) like MOBILITY, POWER SENSITIVITY – defined in TSB-58

Overload Control

Definition of Device and Network Access Priority, Signalling for Network to control access based on priority in overload scenario

Access Channel improvements

Implement R-EACH (BA mode) defined in 1x Rev A to be used with F-PCH, Selective ACK for efficient access channel operation under heavy load

Optimized bearer setup

Optimized SO33 channel setupDirect channel assignment

Idle mode optimizations

Reduced overhead readLonger registration timersLonger SCI

Positioning enhancements

Highly detectable pilot

Motivation for HRPD enhancements

Feature parity with 3G-1x Rev F

• Many 3G-1x Rev F M2M enhancements are already supported in HRPD

• Incremental enhancements needed in HRPD

• Leverage dual mode devices to use HRPD for data demanding M2M applications

• Minimize impact to current deployments and standards

Complement 3G-1x M2M operation

• Power/cost sensitive devices may use 3G-1x SMS trigger for M2M applications using HRPD

• Will benefit from the proposed light weight HRPD session and connection setup procedures

Proposed HRPD M2M Enhancements

M2M personality

Default set of attributes for specific M2M device/application

Avoids session negotiation overhead Set of optimized protocols and attributes common across different M2M

categories

Avoids Session negotiation

Optimized bearer setup

Combine traffic channel allocation with UATIAssignment

Can be leveraged to enable shortlived sessions

Skip session negotiation step using M2M personality feature

Direct traffic channel assignment along with UATI

Optionally tear down session after connection close

Device characteristics Identification

Conveying M2M related device characteristics to ANAssist AN to choose special treatment for M2M devices Encode characteristics in Reserved fields of Default ACMAC header

Enable features based on determined type

HRPD M2M Enhancements – Deeper Dive

Device Characteristics Identification

M2M device characteristics

• Similar to the feature in 1x Rev F• M2M characteristics include• Power Sensitivity• Mobility• Priority• Encode the M2M related characteristics in M2M type Indicator

M2M type indicator

• When is the information needed?• M2M type indicator is needed before session negotiation

• At the time of UATIRequest/Assignment procedures• How to convey it?• Use currently “Reserved” fields in Default ACMAC header

M2M type in Default ACMAC header

• Using the “reserved” field in the Default ACMAC• AN should determine that default ACMAC is being used by the AT

• Not Enhanced ACMAC, the “Reserved” field has been redefined as “Probe Number”

• If UATIRequest comes with RATI (ATIType = RATI) => AT is using Default ACMAC

Default ACMAC header

Enhanced ACMAC header

M2M Personality

M2M personality for avoiding session negotiation overhead• Proposed Mechanism• AT indicates M2M type to AN• AN defaults to M2M personality depending on the M2M type

• Define M2M personality• Standards change needed• Protocol and Attribute defaults suited for M2M – the M2M Personality

• M2M personality (TBD)• Characteristics like

• MFPA or eMFPA?• Long timers – KeepAlive, Slot Cycle index, …• Pre-defined QoS flows based on device priority? ReservationKKIdleState = 0x2?

• May need to define multiple M2M personality types catering to different device characteristics

Optimized bearer setup

Overhead in current bearer setup procedures• Currently following steps are

followed prior to allocation of HRPD bearer to a device• UATI Request and Assignment• Connection Request (CR) and

Traffic Channel Assignment(TCA) for Session Negotiation

• Session Negotiation messaging• Connection Close• CR and TCA for HRPD bearer

• Lot of overhead for M2M devices that establish infrequent connections

• Need a light weight procedure to establish HRPD bearer

Optimized bearer setup using M2M type

M2M device determines it has data to transmit.

1.It sends UATIRequest with RATI. It encodes M2M type in the ACMAC header

Based on the M2M type (4 bit field), the AN chooses appropriate M2M personality set and assigns traffic channel.

2.AN piggy backs TCA with UATI assignment

3.AT acknowledges UATI and Traffic channel assignment

4.HRPD bearer is setup for the device to use for subsequent authentication, M2M data transport etc.