© Alcatel-Lucent | M2M Numbering | April 12, GPP2 M2M TITLE Numbering in 3GPP2 for M2MSOURCE Mike Dolan, Alcatel-Lucent, Mike Dolan, Alcatel-Lucent, This contribution provides a simple approach to supporting certain M2M devices in 3GPP2 networks. 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.

© Alcatel-Lucent | M2M Numbering | April 12, 2010 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

© Alcatel-Lucent | M2M Numbering | April 12, 2010 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.

© Alcatel-Lucent | M2M Numbering | April 12, 2010 Solutions  M2M Class Identifiers  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.  M2M Hierarchical Device Identifiers  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.

© Alcatel-Lucent | M2M Numbering | April 12, 2010 Solutions  Connectionless Communication  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.

© Alcatel-Lucent | M2M Numbering | April 12, 2010 Examples: Example M2M Identifier for a Gas Meter Example M2M Identifier hierarchy

© Alcatel-Lucent | M2M Numbering | April 12, 2010 Examples: Example M2M Messaging Structure

© Alcatel-Lucent | M2M Numbering | April 12, 2010 Examples:

© Alcatel-Lucent | M2M Numbering | April 12, 2010 Examples:

© Alcatel-Lucent | M2M Numbering | April 12, 2010 Summary  M2M Class Identifiers  Use a single value to represent many M2M devices  M2M Hierarchical Device Identifiers  Use an M2M identifier that is hierarchical in nature to select individual device(s)  Connectionless Communication  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.