Machine-to-Machine(M2M) Communication for cdma2000 Systems Orlett W. Pearson, 3GPP2 Liaison Report to TR-50 August 2011

2 | M2M Update | August GPP2 LS to TIA TR-50 3GPP2 M2M Update M2M Activity in 3GPP2: —3GPP2 SC M2M Numbering Ad Hoc. —TSG-S M2M System Requirements —Joint activity: TSG-A, TSG-C, TSG-S and TSG-X **This update will focus on 3GPP2 SC M2M Number**  3GPP2 SC M2M Numbering  The 3GPP2 Numbering and Recommendations Report (SC.P4005-0) document is an analysis of issues associated with M2M Numbering and recommendations from the 3GPP2 SC M2M Numbering Ad Hoc  Noted assumptions:  Backwards compatibility with existing 3GPP2 specifications is expected to be maintained,  Existing Numbering Administration and related guidelines and or procedures e.g., ESN, MEID, UIMID, IMEI are not intended to be affected or require modifications as a result of recommendations in this document.  Industry projections estimate that 50 billion M2M devices will be connected globally using various access technologies by the year 2020.

3 | M2M Update | August GPP2 LS to TIA TR-50 3GPP2 M2M Requirements for consideration  Suggested requirements for 3GPP2 M2M 1x subscription identifiers, included for consideration:  All cdma2000 M2M devices that require a 1x Subscription Identifier should support provisioning with true IMSI.  M2M devices that may roam and that are provisioned with true IMSI should also be provisioned with MIN and MIN-based IMSI.  M2M devices that require a 1x Subscription Identifier shall support provisioning with MIN and MIN-based IMSI.  Suggested requirements for 3GPP2 M2M hardware identifiers included for consideration:  It is recommended that the ESN not be used as an M2M hardware identifier. However, the ESN may be used as an M2M hardware identifier when the ESN numbering resources are already available and where device production allows its use (e.g., end-of-life legacy type implementations).  Every M2M device shall have a globally unique hardware identifier.  Devices with both 3GPP and 3GPP2 operational modes should be assigned only an IMEI (from RR=00 through RR=99) and use that identifier in 3GPP2 modes as the MEID. Alternatively, it is acceptable for a device to have a separate MEID or an ESN for use in 3GPP2 modes.  Devices with only a 3GPP2 operational mode should be assigned only an MEID from range RR=0xA0 and above. Alternatively, it is acceptable for a device to be assigned an ESN.

4 | M2M Update | August GPP2 LS to TIA TR-50 3GPP2 M2M Update  Suggested requirements for 3GPP2 M2M IP identifiers have been included for consideration:  M2M devices should support IPv6 addressing.  In addition to IPv6 addressing, M2M devices may also support IPv4 addressing.  Suggested requirements for MDN (Mobile Directory Numbers) included for consideration:  For M2M devices in 3GPP2 networks that use voice, TDD or analog modem calls operators should ensure sufficient MDN resources are available.  MIN or IMSI addressing should be considered for M2M SMS if operators do not have sufficient MDN resources available.  M2M applications should avoid the use of MDN to the greatest extent possible for inter-technology SMS. One possible solution is to use a mediation device that splits the SMS transaction into a 3GPP2-network part and a 3GPP-network part.  If a cdma2000 operator anticipates a large number of M2M devices subscribing to their service will use VoIP calls in such a way that an MDN will be required, alternative forms of communication that do not require an MDN should be investigated.

5 | M2M Update | August GPP2 LS to TIA TR-50 3GPP2 M2M Update  Suggested requirements for 3GPP2 Card identifiers included for consideration:  Cards designed for M2M devices should not use the UIMID.  If cards are identified with LF_EUIMID/ICCID the cellular operator should be the card issuer for numbering purposes and should allocate portions of the Individual Account Identification Number as needed.  The Individual Account Identification Number shall be allocated by the issuer in ranges matching the number of cards manufactured.  SF_EUIMID codes should only be obtained from the TIA or an administrator authorized to coordinate with the TIA.  The country code used in LF_EUIMID/ICCID codes shall be that of the issuer.  The Issuer Identifier Number shall be allocated by the ITU-T or a national regulator coordinating with the ITU-T.  Ranges of Individual Account Identification Number allocated by the issuer shall be recorded permanently.  Suggested requirements for 3GPP2 RAN identifiers, included for consideration:  The likelihood of SID uniqueness should be maximized by an operator by allocating SID Codes from the appropriate authority (usually a national regulator, contracted third party or IFAST) and ensuring that changes (such as change of ownership of a licensed area identified by a SID) are promptly reported to the same organization.

6 | M2M Update | August GPP2 LS to TIA TR-50 3GPP2 M2M Update  3GPP2 TSG-S M2M System Requirements Discussion in TSG-S on M2M System Requirements continue. The group will review contribution on requirements and/or enhancements related to characteristics and use cases, for example, on:  General requirements,  Architecture requirements,  Addressing  Joint activity: TSG-A, TSG-C, TSG-S and TSG-X During each 3GPP2 face-to-face meeting, a joint session is held to discuss M2M work. The goal is to have this as an End-to-End document which would include air interface, IOS and network components.  Will report more on TSG-S M2M System Requirements and the Joint Activity at the next meeting.