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

Slides:

Advertisements

Similar presentations

TS **): Non-Roaming Reference Architecture for non-3GPP Accesses

Advertisements

Device Trigger Parameters for 3GPP PRO Device_triggering_for_3GPP_presentation Group Name: PRO Source: Tetsuo Inoue, Barbara Pareglio (NEC) ,

oneM2M and AllJoyn Interworking

Submission doc.: IEEE 11-12/0346r1 WLAN and Cellular Interworking and Discovery Use Case Date: Slide 1Joseph Levy, InterDigital Communications,

1 OMA Location Working Group Update Mike Loushine Senior Scientist / Program Manager Emerging Mobile Technologies Group Telcordia Applied Research May.

Service Layer Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP16 Agenda Item:

REQ WG Reuse of underlying networks, 3GPP

REQ WG Reuse of underlying networks, 3GPP

September 2014 Value of the M2M Connection Can LTE Networks be of Value to M2M Applications?

Discussion oneM2M WG2 contributions to address Network Optimization Group Name: WG2 Source: Takanori Iwai, NEC,

OneM2M Draft proposal for slide set. This is not intended to be a oneM2M presentation. It is a collection of source material slides which can be used.

Summary of 3GPP TR GPP2 TSG-S WG4 S Source: Qualcomm Incorporated Contact(s): Anand Palanigounder,

Authors list to be completed.

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

Authors list to be completed.

30-31 March 2005 Workshop "IMS over Fixed Access" - Washington 1 TISPAN_NGN Project plan Martin Niekus Alain Sultan

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

Optimized M2M interworking with mobile networks Group Name: oneM2M REQ Source: Takanori Iwai, NEC, Meeting Date: Agenda.

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

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

T Multimedia Seminar Carlos Herrero55828H Osmo Tolvanen46958L.

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

1 SAE architecture harmonization R RAN2/3, SA2 Drafting Group.

HGI activities transfer to oneM2M Group Name: MAS Source: Patricia MARTIGNE (Orange), Deutsche Telekom, Telecom Italia Meeting Date: Agenda.

Answer the Questions Regarding Pending Issues on Access Control Group Name: WG4 SEC Source: LG Electronics Meeting Date: Agenda Item: SEC#11.4.

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

INTRODUCTION. 1.1 Why the Internet Protocol Multimedia Subsystem 1.2 Where did it come from?

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

WG5 - MAS Progress Report at TP #9 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.

Proposal for WG3 & WG5 work area split

Step by step approach Group Name: WG2 Source: Michael hs. Yang, LG uplus, Jaeseung Song, NEC Europe, Meeting.

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

An introduction to oneM2M

3GPP Rel-13 Interworking discussions

3GPP SCEF Interworking Call Flows

Update on 3GPP RAN3 Multi-RAT joint coordination

Optimized M2M interworking with mobile networks Group Name: oneM2M REQ Source: Takanori Iwai, NEC, Meeting Date: Agenda.

WG5 – MAS#19 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

Streaming Session Support in oneM2M Framework Group Name: WG2 Source: George Foti, Ericsson Meeting Date: Work Item :WI GPP_Rel13_IWK.

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

3GPP SCEF Interworking Discussions

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

Introduction to oneM2M OMA - oneM2M Meeting, San Diego, Jan. 19th 2016

WG5 - MAS Progress Report at TP #8 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.

Submission doc.: IEEE 11-12/0346r2 WLAN and Cellular Interworking and Discovery Use Case Date: Slide 1Joseph Levy, InterDigital Communications,

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#:

Doc.: IEEE /1963r0 Submission May 2007 Gottfried Punz, Siemens AustriaSlide 1 SA2 Status and Interest in IEEE u Date: Authors:

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

WG1 - REQ Progress Report at TP #11 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chairs Meeting Date: to Agenda Item: TP#11,

Management CSF(s) Architectural choices Group Name: WG2 (ARC), WG5(MAS) Source: Catalina Mladin, InterDigital Comm., Meeting.

Introduction to Service Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP8 Agenda Item:

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

Background Data Transfer

3GPP R13 Small Data Delivery

oneM2M Requirements for SCEF northbound API

Update on 3GPP RAN3 Multi-RAT joint coordination

SCEF northbound API Analysis

3GPP interworking in R3 Group Name: ARC

3GPP Rel-13 Interworking discussions

WPM ad-hoc group report TP#25

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

3GPP Interworking Abstraction

TS **): Non-Roaming Reference Architecture for non-3GPP Accesses

ETSI Standardization Activities on M2M Communications

An introduction to oneM2M

3GPP V2X Interworking Potential Impact

ETSI Standardization Activities on M2M Communications

3GPP Update/Status (Release 15 – June 2018)

Presentation transcript:

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

© 2015 oneM2MMARCOM Report oneM2M release 1 specified the use of NSE (Network Services Entity) using the Mcn reference point. In particular for 3GPP: the use of Tsp for triggering of ASN and MN-CSE was specified in 8.4 and annex B of TS0001 for stage 2 aspects. 3GPP Release 11 supports it. In particular for OMA: the use of network location services based on OMA Mobile Location Protocol & OMA RESTful NetAPI for Terminal Location 3GPP release 13 is introducing new features which are relevant for M2M. oneM2M needs to answer two questions: Are oneM2M requirements towards 3GPP covered by those features? Should oneM2M architecture consider 3GPP R13 MTC-related features? – Note1: 3GPP stage2 expected to be finalized summer 2015 – Note2: API definition (see slide 4) is done outside 3GPP, probably by OMA Introduction

© 2015 oneM2MMARCOM Report oneM2M R1

© 2015 oneM2MMARCOM Report 3GPP Architecture Enhancement for Service Exposure – TR IN- CSE Mcn examples of API: sms oneAPI (by GSMA / OMA) Example of 3GPP Network entities currenly under discussion: MTC-IWF via Tsp for device triggering PCRF via Rx for QoS aka AESE HSS via Sh’ for monitoring (IMEI-IMSI), aka MONTE location monitoring via HSS or MME/SGSN BM-SC via MB2 for group communications, aka GROUPE MTC- IWF Tsp PCRF Rx HSS S6m MME/ SGSN MONTE TR BM-SC MB2 GROUPE TR AESE TR T6(?)

© 2015 oneM2MMARCOM Report Additional info list of AESE features: – Setting up an AS session with required QoS – Support of 3rd party for predictable communication patterns description – Informing the 3rd party about a UE's connection properties – Informing the 3rd party about potential network issues – 3GPP resource management for background data transfer List of MONTE monitoring events, cofigurable in the 3GPP network: – Roaming status, and Serving Network of the UE – Change in association of the MTC Device and UICC – Location of the UE – Loss of connectivity – UE Reachability – Communication Failure – Reporting the number of UEs present in a certain area 5