REQ WG Reuse of underlying networks, 3GPP

Slides:

Advertisements

Similar presentations

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

Advertisements

REQ WG Reuse of underlying networks, 3GPP

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

IMS Service Discovery over PADP

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

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.

Report of ETSI NGN IPTV activities Rainer Münch, TISPAN Chairman Presenter: Ian Spiers DOCUMENT #:GSC13-PLEN-56 FOR:Presentation SOURCE:Rainer Münch, Ian.

1 | 3GPP2 TSG-X Discussion | December GPP2 X R1 TITLE: TITLE: M2M Deployment Scenarios for 3GPP2SOURCE Mike Dolan, Alcatel-Lucent,

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

Authors list to be completed.

ATIS & TISPAN JOINT MEETING ON NGN Washington D.C., 1 April 2005 MEETING SUMMARY Draft v2 (4 April 2005) Based on Notes from David Boswarthick (ETSI),

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

Unrestricted Connection manager MIF WG IETF 78, Maastricht Gaëtan Feige, Cisco (presenter) Pierrick Seïté, France Telecom -

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

Network Resource Gateway (NRG) Application DevelopmentDSLD Unit Florin van Slingerland Rev A Slide 1 Application Development Presentation/Course Teaser.

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:

Status of Active New Work Items Group Name: WPM Source: Karen Hughes, ETSI Meeting Date:

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

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.

1 3GPP2 GBA Overview Adrian Escott Chair, TSG-S WG4 24 May 2006.

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.

An introduction to oneM2M

3GPP Rel-13 Interworking discussions

3GPP SCEF Interworking Call Flows

IMS developments in 3GPP

Routing Problem of the Current Architecture Group Name: ARC Source: Hongbeom Ahn, LG Electronics, Meeting Date: Agenda.

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

WG5 – MAS#21 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.

WG1 status report to TP#20 Group Name: oneM2M TP20 Source: Joerg Swetina (NEC) Meeting Date: to Agenda Item: TP#19, Item 10.4, Reports.

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

Author: Tobias Kaufmann, Bundesnetzagentur / Federal Network Agency Standardisation of Public Safety in 3GPP.

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

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

Directions for Release 3 Group Name: SEC Source: NEC Europe Ltd. Meeting Date: SEC22, Agenda Item: Discuss directions.

3GPP TSG RAN WG2 meeting #92 Nanjing, China 23-27, May 2016 R

IEEE SISWG (P1619.3)‏ Messaging & Transport. AGENDA Transport Protocols & Channel Protection Messaging Layer Capability Exchange & Authentication Groups.

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

SCEF northbound API Analysis

3GPP interworking in R3 Group Name: ARC

Possible options of using DDS in oneM2M

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,

China Communications Standards Association ZTE Corporation, P.R. China

3GPP Interworking Abstraction

ETSI Standardization Activities on M2M Communications

3GPP V2X Interworking Potential Impact

ETSI Standardization Activities on M2M Communications

Presentation transcript:

REQ WG Reuse of underlying networks, 3GPP Contact: Omar Elloumi (ALU), Joerg Swetina (NEC), Puneet Jain (Intel) Source: Alcatel-Lucent (ATIS), NEC (TTC), NEC Europe (ETSI), Intel (ATIS) Meeting Date: 2015-03-23 Agenda Item:

Introduction oneM2M release 1 specified the use of NSE (Network Services Entity) using the Mcn reference point. Using interfaces provided by 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. Using interfaces provided by OMA: the use of network location services based on OMA Mobile Location Protocol & OMA RESTful NetAPI for Terminal Location For oneM2M release 2 oneM2M requested 3GPP to consider new features as part of their Rel-13 work. oneM2M sent Liasion to 3GPP SA1/SA2/SA3 on interactions of oneM2M with Underlying Networks (oneM2M-TP-2013-0307R01/S2-140017) 3GPP release 13 is introducing new features which are relevant for M2M as part of several work items – AESE, MONTE, GROUPE (please refer slide 5, 6) but OMA did not clearly commit to create / modify their APIs to include 3GPP release 13 changes.

oneM2M R1 / 3GPP Rel-11

Features under discussion at 3GPP list of AESE features (3GPP TR 23.708): Service Capability Exposure Framework architecture Setting up an AS session with required QoS Change of chargeable party at the session setup or during the session Support of 3rd party interaction on information for predictable communication patterns 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, configurable in the 3GPP network (3GPP TR 23.789): 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

Features under discussion at 3GPP list of GROUPE features (3GPP TR 23.769): Message delivery for group of devices Group based policy control Group specific NAS level congestion control Group based addressing and identifier

oneM2M Rel-2 / 3GPP Rel-13 examples of API: sms oneAPI (by GSMA / OMA) oneM2M IN-CSE 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 oneM2M IN-CSE oneM2M Mcn AESE TR 23.708 MONTE TR 23.789 GROUPE TR 23.769

To do: oneM2M needs to answer following questions: Are oneM2M requirements towards 3GPP covered by those features? How oneM2M architecture incorporates 3GPP R13 MTC-related features? Note1: 3GPP stage2 expected to be finalized May, 2015 Note2: API definition (see slide 6) is done outside 3GPP, <probably by OMA> oneM2M should request clarification [from OMA and 3GPP] if 3GPP R13 MTC-related features (SEES,AESE,GROUPE,MONTE) will be exposed via a SCEF and if OMA will specify the API such that oneM2M Rel-2 can make use of it.