3GPP Rel-13 Interworking discussions

Group Name: TP #18Source: Rejesh Bhalla, ZTE Corporation, rabhalla@ztetx.comMeeting Date: 2015-07-21Agenda Item: TBD

Background Information

• Incoming LS from 3GPP SA2– TP-2015-0732

• Incoming LS from OMA ARC WG– TP-2015-0749

• oneM2M WI: 3GPP Rel-13 Interworking– TP-2015-0694R02

Incoming LS from 3GPP SA2

• Incoming LS from 3GPP SA2 informs about work done during Rel-13 on MTC features:– Features that allow an application to take advantage of the

service capabilities provided by the 3GPP system– AESE, MONTE, GROUPE and HLCom features – 3GPP TS 23.682 (version 13.2.0 or later) includes Stage-2

aspects for these features. Stage-3 work will be progressed by 3GPP CT WGs

– LS is addressed to GSMA, OMA and oneM2M

© 2014 oneM2M Partners<Document number>

3

3GPP AESE Feature• Architecture Enhancements for Service capability Exposure

– Service Capability Exposure Function (SCEF) entity provides a means to expose the services and capabilities provided via 3GPP interfaces

– Specifically, solutions have been provided for the following:• Support for setting up an AS session with required QoS• Support for changing the chargeable party at session set-up or during the

session• Support of 3rd party interaction on information for predictable

communication patterns• Support for informing a 3rd party about potential network issues • Support for 3GPP resource management for background data transfer

3GPP MONTE and HLCom features

• Monitoring Enhancements (MONTE)– Intended for monitoring of specific events in the

3GPP system and making such monitoring events information available via the SCEF

• High Latency Communication (HLCom)– Solution for downlink access for devices that are not

reachable for a long period e.g. due to device applying Power Saving techniques

3GPP GROUPE feature

• Group based Enhancements (GROUPE)– Solutions for group level NAS congestion control

(internal 3GPP function – no action by oneM2M)– Solutions for message delivery for a group of

devices using MBMS – SCS/AS uses an API to the SCEF to access MBMS

services

3GPP architecture for Service Capability Exposure

HSS PCRF

SMS-SC/ GMSC/ IWMSC

MME/SGSN

MTC-IWF

S-CSCF Network Entity

S6t Rx T4/ Tsms

T6a/T6b

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

BM-SC

MB2

Possible areas of focus for us • SCEF internal architecture and APIs to expose 3GPP

service capabilities via SCEF have NOT been specified by SA2– 3GPP SA2 has defined some expected behaviour of SCEF

though

• SA2 invites GSMA, OMA and oneM2M to consider the creation of APIs– The need to define and specify SCEF internal capabilities

also for using the APIs

3GPP architecture for Service Capability Exposure

HSS PCRF

SMS-SC/ GMSC/ IWMSC

MME/SGSN

MTC-IWF

S-CSCF Network Entity

S6t Rx T4/ Tsms

T6a/T6b

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

BM-SC

MB2

Target SDOsAreas of Focus

oneM2M Work Item• oneM2M Work Item # 0037: 3GPP_Rel13 Interworking

– Objective: To produce an interworking specification between oneM2M architecture and 3GPP Rel-13 architecture for Service Capability Exposure defined in TS 23.682

• Different deployment scenarios where SCEF is hosted by MNO, or when it is hosted by M2M Service Provider or when it is hosted by a 3rd party service provider to be considered – IN CSE connected to the SCEF using APIs (e.g. APIs defined by OMA) or

via APIs to be defined by oneM2M <??> (Option 1) • Scenario when SCEF is hosted by MNO or by a 3rd party service provider

– IN-CSE acts as SCEF i.e. oneM2M CSEs interfaces directly with the 3GPP network (Option 2)

• Scenario when SCEF is hosted by 3rd party service provider

oneM2M Layered Model

Application Layer

Common ServicesLayer

Network ServicesLayer

oneM2M Functional Architecture

AE AE

Mca Mca Mca

Mcc

Mcn Mcn

CSE CSE

NSE NSE

Field Domain Infrastructure Domain

To Infrastructure Domain of other Service Provider

Mcc’

Interworking Architecture – Option 1

Interworking Architecture – Option 2

Scope of our work ...• Interworking Architecture

– Architecture Assumptions

– Architecture framework for different deployment options • Expected work areas:

– APIs: ??– SCEF

• Northbound interface with IN CSE• Use of southbound 3GPP interfaces as in 3GPP TS 23.682• Internal SCEF logic for different service exposure use cases• Others ??

– IN CSE• Procedures for exposing different service exposure use cases• Others ??

Scope of our work ..• Use cases related to AESE, MONTE, GROUPE and

HLCom features as in 3GPP TR 23.682– Develop oneM2M specific solutions

• Solution component related to the IN CSE• Solution component related to the SCEF• Solution component related to the interface between IN-CSE and

the SCEF• Leverage solutions already specified in 3GPP TS 23.682 on 3GPP

specific interfaces• Others ??

• oneM2M specific use cases

Anything we missed …

•

Thanks

•