1. 3GPP Rel-13 Interworking discussions Group Name: TP #18 Source: Rejesh Bhalla, ZTE Corporation, rabhalla@ztetx.com Meeting Date: 2015-07-21 Agenda Item: TBD

2. Background Information Incoming LS from 3GPP SA2 – TP-2015-0732 Incoming LS from OMA ARC WG – TP-2015-0749 oneM2M WI #0037: 3GPP Rel-13 Interworking – TP-2015-0694R02

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

4. 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 3 rd party interaction on information for predictable communication patterns Support for informing a 3 rd party about potential network issues Support for 3GPP resource management for background data transfer

5. 3GPP MONTE and HLCom features Monitoring Enhancements (MONTE) – 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

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

7. 3GPP architecture for Service Capability Exposure

8. Possible areas of focus 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 has invited GSMA, OMA and oneM2M to consider the creation of APIs – The need to define and specify SCEF internal capabilities also for using the APIs

9. 3GPP architecture for Service Capability Exposure Target SDOs Areas of Focus

10. Incoming LS from OMA ARC WG Incoming LS from OMA ARC WG informs about a new work item (ENCap-M2M) regarding Network APIs that would expose network capabilities to oneM2M and other applications – APIs (and SCEF) per 3GPP requirements

11. 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 such as SCEF hosted by MNO, hosted by oneM2M Service Provider or hosted by a 3 rd party service provider to be considered – IN-CSE interfaces with the SCEF using OMA defined APIs or using APIs defined by oneM2M/other party (Arch Option 1) Addresses scenario of SCEF hosted by MNO or by a trusted 3 rd party service provider – IN-CSE acts as an SCEF i.e. IN-CSE interfaces directly with the 3GPP network (Arch Option 2) Addresses scenario when SCEF is hosted by trusted oneM2M service provider

12. oneM2M Layered Model

13. oneM2M Functional Architecture

14. Interworking Architecture – Arch Option 1

15. Interworking Architecture – Arch Option 2

16. Interworking Architecture

17. Areas of Focus

18. Scope of work... Architecture framework – Support for all deployment scenarios – Support for relevant OMA specified APIs – Support for other APIs – Access control IN-CSE: – Arch Option 1: Southbound interfaces: OMA specified or other APIs. Possible input to OMA for other APIs. Northbound interfaces: TBD – Arch Option 2: Southbound interfaces: 3GPP exposed interfaces. Possible input to 3GPP. Northbound interfaces: TBD. Other exposure function: – For supporting other APIs (Arch Opt 1), Southbound interfaces: 3GPP exposed interfaces or other underlying network exposed interfaces. Northbound interfaces: other APIs.

19. Scope of work.. Identify use cases related to AESE, MONTE, GROUPE and HLCom features as in 3GPP TR 23.682 that need to be supported by oneM2M – Each such use case identified as a ‘Key Issue’ – Leverage solution guidelines in 3GPP TS 23.682 for developing oneM2M specific solution(s) for each Key Issue – … Identify other use cases for service exposure from 3GPP network (timeline TDB) – Each such use case identified as a ‘Key Issue’ – Develop solution(s) for each such Key Issue

20. Thanks