© alcatel-lucent 2010 1 | m2m numbering | april 12, 2010 3gpp2 m2m-20100412-004 title numbering in...

1 | M2M Numbering | April 12, 2010 © Alcatel-Lucent 2010

3GPP2 M2M-20100412-0043GPP2 M2M-20100412-004

TITLETITLE

Numbering in 3GPP2 for M2MSOURCESOURCE

Mike Dolan, Alcatel-Lucent, Mike Dolan, Alcatel-Lucent, [email protected]@alcatel-lucent.com ABSTRACTABSTRACT

This contribution provides a simple approach to supporting certain M2M devices This contribution provides a simple approach to supporting certain M2M devices in 3GPP2 networks.in 3GPP2 networks.

RECOMMENDATIONRECOMMENDATION

Discuss and adopt in principle.Discuss and adopt in principle.

© 2010 Alcatel-Lucent © 2010 Alcatel-Lucent

Alcatel-Lucent grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained 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 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 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-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 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. 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 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 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.material contained herein and to any intellectual property of Alcatel-Lucent other than provided in the copyright statement above.


Outline

Issues

M2M Device Identities vs. CDMA address space

Congestion on CDMA control channels

Solutions

M2M Class Identifiers

M2M Hierarchical Device Identifiers

Connectionless Communication

Security

Examples

Summary


Issues: Identifiers and Congestion

M2M Device Identities vs. CDMA address space

Simply put, there aren’t enough CDMA radio level identifiers to assign one to each M2M device.

Congestion on CDMA control channels

Signaling to multiple M2M devices individually will consume large amounts of processing and control channel space leading to congestion and loss of service to regular subscribers.


Solutions


Proposal: Use a limited number of existing radio interface identifiers to represent classes of M2M devices, e.g., a single MEID may be used to represent all gas meters.

All M2M devices in the same class, i.e., having the same radio interface identifier (e.g., MEID=9999), use common slot cycles, sleep periods, access classes, etc., so that they can be controlled as a group.


Embed a separate M2M identifier within the content of the signaling message that is hierarchical in nature.

Allow wildcarding of one or more components of the M2M identifier to allow communication with subsets of M2M devices belonging to the same class, e.g., all gas meters with the same model number.

Use connectionless communications between the network and the M2M device.


Solutions


The M2M devices would not attach to the network, but only communicate on a “datagram” basis.

The RAN is aware of a class of M2M devices having a single identifier, e.g., the same MEID, but is not provisoned with the identities of the individual devices, nor aware of their presence in its area except during specific communications.

The RAN addresses the devices using the single M2M class identifier, and recognizes communications from those devices by that same identifier. It can also address individual M2M devices using a combination of the M2M class identifier and a unique M2M identity.

Security

There would be two keys that would be useful: an M2M application layer key, and a RAN level key.

The M2M Application Key is used to secure the message content, e.g., a gas meter reading. It would be provisioned into the device and be known to an M2M application server.

The RAN level key would be used to secure the signaling message sent over the radio. It would be provisioned into all devices belonging to the same class and be know to the RAN.


Examples:

Class of Devices

SubclassSub-

SubclassUnique Identity

...

Gas Meters Manufactured by xyz

Model Number

Serial Number

Example M2M Identifier for a Gas Meter

Example M2M Identifier hierarchy


Examples:

M2M Identity M2M Application Contents

M2M Class ID. M2M Message Contents

Example Uplink M2M Communication from an

M2M Device to the Wireless Network

IP Address M2M Message Contents

Example Uplink M2M Communication from the Wireless Network to the M2M Application Server

Action

Action

Example M2M Messaging Structure


Examples:

Wireless Network

M2M Application Server Q

M2M Application Server R(acting as a routing function

using subfields of the M2M identifier)

M2M Application Server S

M2M Device


Examples:

Wireless NetworkM2M Device=A

M2M Device=B

M2M Device=C

M2M Class=1

M2M Class=1

M2M Class=1

Appl. Key = xxx

Appl. Key = yyy

Appl. Key = zzz

Network Key = aaa

Network Key = aaa

Network Key = aaa

M2M Devices

M2M Class=1Network Key = aaaM2M Appl. IP = mmm

M2M Class=2Network Key = bbbM2M Appl. IP = nnn

M2M Appl. ServerAppl. Key = aaaIP Addr = mmm

M2M Appl. ServerAppl. Key = bbbIP Addr = nnn


Summary


Use a single value to represent many M2M devices


Use an M2M identifier that is hierarchical in nature to select individual device(s)


Some M2M devices are stationary and have short, infrequent communications.

These devices do not attach to the network, and simply send “datagrams”.

Security

An M2M application level key, and a RAN level key are provisioned.

The Application level key is unique to the device. The RAN level key is unique to the M2M Class.

© alcatel-lucent 2010 1 | m2m numbering | april 12, 2010 3gpp2 m2m-20100412-004 title numbering in...

Documents