REQ WGReuse 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-23Agenda Item:

© 2015 oneM2MMARCOM Report

• 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.

Introduction

Microsoft Word 97 - 2003 Document

© 2015 oneM2MMARCOM Report

oneM2M R1 / 3GPP Rel-11

•

© 2015 oneM2MMARCOM Report

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

4

© 2015 oneM2MMARCOM Report

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

5

© 2015 oneM2MMARCOM Report

oneM2M Rel-2 / 3GPP Rel-13• 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 QoSaka 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

GROUPETR 23.769

HSS PCRF

SMS-SC/ GMSC/ IWMSC

MME/ SGSN

MTC-IWF

S-CSCF Network Entity

Sh Rx T4/ Tsms

Tx Tsp ISC

...

3GPP interface

3GPP TRUST DOMAIN

Service Capability Exposure Function

API 1 API 2 API 3 API n ...

Application

Application Application

OMA/ GSMA/

other SDOs

oneM2M IN-CSE

oneM2M IN-CSE

oneM2M Mcn

MONTE TR 23.789

AESE TR 23.708

© 2015 oneM2MMARCOM Report

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, 2015Note2: 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.

To do: