An operator’s perspective on support for different M2M deployment scenarios AT&T Group Name: TP Source: Farooq Bari, Jianrong Wang; AT&T;

Slides:

Advertisements

Similar presentations

Steve Jordan Director. Industry Solutions 05/05/14 Managing Chaos: Data Movement in 2014.

Advertisements

Problem of non-Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.0 Agenda Item: TBD.

© 2003 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

REQ WG Reuse of underlying networks, 3GPP

REQ WG Reuse of underlying networks, 3GPP

REQ WG Reuse of underlying networks, 3GPP From: Omar Elloumi (ALU) Source: Alcatel-Lucent (ATIS) Meeting Date: Agenda Item:

Discussion on LI for Mobile Clouds

Celoxis Intro Celoxis is a web-based project management software company based in India. The Celoxis application integrates management of projects, resources,

M2M Global Initiative OneM2M April 24, 2012

OneM2M-ARC BRequest_Resource Architecture Proposal to address Broadcasting/Multicasting Requirements Group Name: WG2 Source: Takanori Iwai, NEC,

Mobile Communication Congestion Exposure Scenario

RoA and SoA Integration for Message Brokers Group Name: WG2-ARC Source: ALU Meeting Date: Agenda Item:

Mechanism to support establishment of charging policies Group Name: WG2-ARC Source: InterDigital Meeting Date: TP8 Agenda Item:

Progressing the Work on the MAS TR-0006, TR-0007 Group Name: Management Abstraction and Semantics Source: Tim Carey, ALU,

Step by step approach Group Name: WG2

Focus on developing RESTful API Group Name: TP Source: Shingo Fujimoto, FUJITSU (TTC), Meeting Date: Agenda Item:

An Operators Input for oneM2M Baseline  Group name: TP#2/WG1  Source: DTAG, Vodafone Group  Meeting Date:  Agenda Item: WG1 agenda item.

A Unified Framework for Software Defined Information-centric Network Wen Qi, Jinfan Wang, Yujia Luo, Rui Qin, Weigang Hou, Jing Ren Shucheng Liu, Jianping.

Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:

Group Meeting Ming Hong Tsai Date : Toward Ubiquitous Massive Accesses in 3GPP Machine-to- Machine Communications 2.

Proposed Co-convened WG1/2 Objectives, Schedule, and Activities Group Name: TP#1 Source: Omar Elloumi (Alcatel-Lucent), Laurent Laporte (Sprint) Meeting.

3GPP Rel-13 Interworking discussions

Considerations on M2M URIs Group Name: WG2(ARC) Source: Yong-Suk Park, Sung-Chan Choi, Jaeho Kim, KETI, Meeting Date:

Discussion on the problem of non- Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.2.

WG 2 Progress Report at TP #8 Group Name: oneM2M TP #8 Source: WG2 leadership Meeting Date: /13 Agenda Item: WG Reports.

Doc.: 802_Handoff_Architecture_Elements_r2 Submission May David Johnston, IntelSlide 1 Architectural Elements of an 802 Handoff Solution David Johnston.

Jeju, 13 – 16 May 2013Standards for Shared ICT TIA TR-50 M2M-Smart Device Communications Dr. Jeffery Smith Chief Innovation and Technology Officer/EVP.

Work Group / Work Item Proposal Slide 1 © 2012 oneM2M Partners oneM2M-TP oneM2M_Work_Group_Work_Item_Proposal Group name: Technical Plenary Source:

Proposal for WG3 & WG5 work area split

Overview of analysis of existing SDO M2M architectures Group Name: REQ ARC#2 Source: Alcatel-Lucent.

Node-Specific Resource Group Name: ARC&MAS Source: LGE, Meeting Date: Agenda Item: Contribution.

Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,

An introduction to oneM2M

WG 2 Progress Report at TP#9 Group Name: oneM2M TP #9 Source: WG2 leadership Meeting Date: /21 Agenda Item: WG Reports.

3GPP Rel-13 Interworking discussions

Role Based Access Control In oneM2m

WG-2 - ARC TP #18 Status Report Group Name: oneM2M TP #18 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.

M2M Service Subscription Profile Discussion Group Name: oneM2M TP #19.2 Source: LG Electronics Meeting Date: Agenda Item:

Release Timeline Discussion R2 and beyond Group Name: TP_WPM Source: Roland Hechwartner, WPM Convenor, Meeting Date:

SE abstraction scenarios Group Name: SEC Source: Claus Dietze, Giesecke & Devrient Meeting Date: Agenda Item: WI SE abstraction.

Architectural Considerations for Semantic Support Group Name: WG5 Source: Martin Bauer (NEC), Joerg Swetina (NEC) Meeting Date: Agenda Item:

Discussion about RESTful Admin API Group Name: SEC & ARC Source: FUJITSU Meeting Date: Agenda Item: Device Configuration.

Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,

CERES-2012 Deliverables Architecture and system overview 21 November 2011 Updated: 12 February

M2M Service Layer – DM Server Security Group Name: OMA-BBF-oneM2M Adhoc Source: Timothy Carey, Meeting Date:

Admin API for Secure Environment Group Name: SEC Source: Giesecke & Devrient Meeting Date:

Proposed Co-convened WG1/2 Objectives, Schedule, and Activities Group Name: TP#1 Source: Omar Elloumi (Alcatel-Lucent), Laurent Laporte (Sprint) Meeting.

Device Management Deployments In oneM2m Group Name: MAS Working Group Source: Timothy Carey, Alcatel-Lucent, Meeting Date:

3GPP SCEF Interworking Discussions

Company LOGO Network Architecture By Dr. Shadi Masadeh 1.

Status of Active Work Items Level of Completeness Group Name: WPM Source: Roland Hechwartner, WPM Convenor Updated:

oneM2M based IoT Platform Development of SK Telecom

Group Name: oneM2M WG1 Requirements Source: Phil Hawkes, Rapporteur “Benefits of oneM2M technology” TR,

Adding Non-blocking Requests Contribution: oneM2M-ARC-0441R01R01 Source: Josef Blanz, Qualcomm UK, Meeting Date: ARC 7.0,

WG5 – MAS#22 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Tim Carey(Alcatel-Lucent, WG5 Vice Chair) Meeting Date:

Reasons for CSF Clean-up (Issues & Next Steps) Group Name: WG2 Source: Syed Husain – NTT DOCOMO Meeting Date: (ARC_9.3) Agenda Item: 6 DOC#:

DM Collaboration – OMA & BBF: Deployment Scenarios Group Name: WG5 - MAS Source: Tim Carey, ALU, Meeting Date:

Proposed Process for Forming the oneM2M Baseline  Group name: TP#1  Source: Laurent Laporte, Sprint,

Jeju, 13 – 16 May 2013Standards for Shared ICT TTA M2M Activities & Proposal of revised resolution Peter J. Kim, Principal Specialist, TTA Document No:

3GPP Rel-13 Interworking discussions Group Name: TP #18 Source: Rejesh Bhalla, ZTE Corporation, Meeting Date: Agenda Item:

Background Data Transfer

3GPP interworking in R3 Group Name: ARC

Possible options of using DDS in oneM2M

3GPP Rel-13 Interworking discussions

OneM2M-ARC BRequest_Resource Architecture Proposal to address Broadcasting/Multicasting Requirements Group Name: WG2 Source: Takanori Iwai,

Update from TR-45.5 on IMT Standardization

TTA M2M Activities & Proposal of revised resolution

3GPP V2X Interworking Potential Impact

TIA TR-50 M2M-Smart Device Communications

Presentation transcript:

An operator’s perspective on support for different M2M deployment scenarios AT&T Group Name: TP Source: Farooq Bari, Jianrong Wang; AT&T; Meeting Date: Agenda Item: 7. Contributions

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

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.

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

A possible Mobile Operator’s Deployment Scenario

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

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.

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