1. An operator’s perspective on support for different M2M deployment scenarios AT&T Group Name: TP Source: Farooq Bari, Jianrong Wang; AT&T; farooq.bari@att.com; jianrong.wang@att.com;farooq.bari@att.comjianrong.wang@att.com Meeting Date: 2012-12-10 Agenda Item: 7. Contributions

2. OneM2M has recently started the process of gathering requirements based on which m2m service architecture shall be developed. This presentation provides an operator’s perspective on different deployment scenarios that can lead to operational requirements at stage 1, or architectural requirements at stage 2, or both. © 2012 oneM2M Partners 2 Introduction

3. M2M Deployment Scenarios An M2M system can be viewed in more than one ways depending upon the perspective One possible way of looking at M2M system is to consider various deployment scenarios and the interaction between different M2M player’s in those deployments To allow M2M service providers to easily access the service capabilities provided by underlying networks, these interactions occur over interfaces and APIs at the boundaries between different business entities e.g. between network operators and M2M service providers. Depending upon the deployment scenarios the boundaries can shift and hence the type of interaction can also change. To maintain a healthy M2M ecosystem, while developing service architecture, oneM2M needs to take into consideration all viable deployment scenarios so that appropriate interfaces and APIs needed for such deployments are developed.

4. 3GPP’s M2M Deployment Scenarios 3GPP has considered three deployment models with different levels of interaction between a mobile network operator and an M2M service provider

5. A possible Mobile Operator’s Deployment Scenario

6. Benefits of this approach Close cooperation between network operators and software development community Quick deployment and adoption of new features rolled out by operators – always beta Differentiation amongst operators based on different capabilities providing healthy competition

7. Possible solution OneM2M works closely with entities like 3GPP to – Support interfaces such as Tsp that can allow following type of capabilities to be made available to the service layer Device triggering and small data transmission Device monitoring e.g. Device Location Group based management – Support existing roaming models for delivery of M2M services OneM2M standardizes a generic mechanism (for example a container via an API) that allows M2M service providers to interface to the capabilities provided by the underlying networks in deployment model 2 and 3 in order to quickly roll out new capabilities to the community of software developers.

8. Way Forward Discuss and agree in principle to support for  Different deployment scenarios for M2M services  Service, operational and architectural requirements to support these deployment scenarios