Streaming Session Support in oneM2M Framework Group Name: WG2 Source: George Foti, Ericsson Meeting Date: 2015-08-15 Work Item :WI-0037 3GPP_Rel13_IWK.

Slides:

Advertisements

Similar presentations

SEC Clarification Group Name: WG4 (SEC-2014-xxxx) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:

Advertisements

Is a Node or not Node? ARC Node_resolution Group Name: ARC Source: Barbara Pareglio, NEC, Meeting Date: ARC#9.1 Agenda.

Omniran GPP Trusted WLAN Access to EPC Use Case Analysis Date: Authors: NameAffiliationPhone Max RiegelNSN

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

ITU Workshop on "Future Trust and Knowledge Infrastructure", Phase 1 Geneva, Switzerland, 24 April 2015 Session 4 – IoT data platform based on oneM2M Dr.

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

Method of Converting Resource definitions into XSD Group Name: WG3 (PRO) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

Multi-Link Devices Group Name: WG1 Source: Kaonmedia, KETI Contact: Hwang Kwang Tae Yong-Suk Park

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

2-levels Access control for HTTP binding Group Name: WG4 (& WG2/WG3 for information) Source: Shingo Fujimoto, FUJITSU, Meeting.

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

PRO R01-URI_mapping_discussion Discussion on URI mapping in protocol context Group Name: PRO and ARC Source: Shingo Fujimoto, FUJITSU,

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.

Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: Agenda Item: Management.

TS0001 Identifiers way forward Group Name: WG2 Source: Elloumi, Foti, Scarrone, Lu (tbc), Jeong (tbc) Meeting Date: Agenda Item: ARC11/PRO11.

Experience and Discussion on Interworking Proxy Implementation Group Name: WG2 Source: Korea Electronics Technology Institute (KETI) Meeting Date: ~24.

Response Status Codes Concepts for oneM2M Group Name: WG3 Source: Philip Jacobs, Cisco, Meeting Date: Agenda Item: TS-0004.

Fuctional Procedure for oiC interworking

WG 3 Progress Report at TP #7 Group Name: oneM2M TP #7 Source: Raymond Forbes, LM Ericsson, Meeting Date: /18 Agenda.

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

Primitive End-to-End Security Requirements Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting.

An introduction to oneM2M

OneM2M Challenges of M2M Security and Privacy

Interactive Connectivity Establishment : ICE

Interworking with an External Dynamic Authorization System Group Name: SEC WG Source: Qualcomm Inc., Wolfgang Granzow & Phil Hawkes Meeting Date: SEC#20.2,

3GPP Rel-13 Interworking discussions

OIC device management interworking procedure

OIC INTERWORKING OPERATIONAL PROCEDURE (ADDRESSING AND DISCOVERY) Group Name: Architecture WG Source: Kiran Vedula, Samsung Electronics,

M2M Service Session Management (SSM) CSF

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

WG-2 - ARC TP #18 Status Report Group Name: oneM2M TP #18 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.

Security API discussion Group Name: SEC Source: Shingo Fujimoto, FUJITSU Meeting Date: Agenda Item: Security API.

Page 1TTT - May 12, GPP IMS Standardization Update Bell Labs Innovations Lucent Technologies Room 9C Lucent Ln. Naperville, IL E Mail.

Issue regarding authentication at MN-CSE Group Name: ARC & SEC Source: FUJITSU Meeting Date: Agenda Item: Security Admin API.

3GPP SCEF Interworking Discussions

M2M Service Session Management (SSM) CSF Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP8 Agenda Item:

Attribute-level access control Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 16 Agenda Item: TBD.

CMDH and Policies Contribution: oneM2M-ARC-0603

FUCTIONAL ARCHITECTURE FOR OIC INTERWORKING Group Name: Architecture WG Source: Jieun Keum, Samsung Electronics,

Issues about management Group Name: MAS9.2 Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item:

Subscription and Notification Issue Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: ~23 Agenda Item:

Consideration Security Issues on Registration Group Name: WG4 (SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

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

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

Possible Solution of Interworking between oneM2M and OSGi

Omniran CF00 1 Key Concepts of Association and Disassociation Date: Authors: NameAffiliationPhone Max RiegelNokia

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

Possible options of using DDS in oneM2M Group Name: ARC Source: KETI, Huawei, Hitachi, China Unicom Meeting Date: Agenda Item: DDS binding.

Specifying the Address of Management Client of Managed Entity Group Name: ARC Source: Hongbeom Ahn, SK Telecom, Meeting Date: TP#21 Agenda.

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

Background Data Transfer

Update on 3GPP RAN3 Multi-RAT joint coordination

SIP for Grid networks Franco Callegati, Aldo Campi, Walter Cerroni

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

3GPP interworking in R3 Group Name: ARC

Possible options of using DDS in oneM2M

Issues of <locationPolicy> Discussion

MAF&MEF Interface Specification discussion of the next steps

3GPP Rel-13 Interworking discussions

3GPP Interworking Abstraction

Service Layer Dynamic Authorization [SLDA]

Development Guideline for oneM2M Products and Services

3GPP V2X Interworking Potential Impact

3GPP Interworking and use of <schedule> resource

Summary of the MAF and MEF Interface Specification TS-0032

Presentation transcript:

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

Introduction Streaming sessions are negotiated and can be classified as follows: – Streaming session with No peer to peer negotiation of session Single Offer in originating request The target application must accept the offer or reject the offer and consequently the request – Streaming Session with peer to peer Negotiation of session Multiple Offers in Originating Request The target application must accept one of the offers or reject all and subsequently the request

Streaming Sessions Streamed data does not traverse the oneM2M layer, rather directly between applications under control of the oneM2M layer.

Streaming Session - Architectural Impacts Network Domain Network Applications Core Network Connection MN-SCE Core Network Connection 3GPP Core Network Mcn (Rx) PCRF IN-CSE Packet Network Gx Impacts: IN-CSE to support Rx (3GPP TS ), or equivalent API Mca, Mcc to support media description attribute parameter based on SDP (RFC 4566) IN-CSE maps the media description to Rx according to 3GPP rules ADN Mcc Mca

Streaming Session – Deployment 1 Network Domain Network Applications MN-CSE PCRF NSCL Gx/Gac ADN – Control ADN - Media Network Application Media Network Application Control Packet Core network Nodes IN-CSE Mcc Mca Internal Mca 3GPP Core Network Mcn (Rx)

Streaming Session – Deployment 2 Network Domain Network Applications PCRF NSCL Gx/Gac ADN – Control ADN - Media Network Application Media Network Application Control Packet Core network Nodes IN-CSE Mca Internal Mca 3GPP Core Network Mcn (Rx)

Streaming Session – Deployment 3 Network Domain MN-CSE PCRF NSCL Gx/Gac ADN – Control ADN - Media Packet Core network Nodes IN-CSE Mcc Mca Mcc 3GPP Core Network MN-CSE ADN – Control ADN - Media Mca Mcn (Rx)

Streaming Session Procedure – Deployment 1 MN-CSE NA IN-CSE Register with MN_CSE CREATE-Streaming-Session (media-description, Target AE-ID, Originating AE-ID, Session-ID) PCRF ADN Register with IN_CSE CREATE-Streaming-Session (media-description, Target AE-ID, Originating AE-ID, Session-ID) NOTIFY Target AE-ID, Originating AE-ID, Session- ID) Response OK CREATE-Streaming-Session (media-description, Target AE-ID, Originating AE-ID, Session-ID) The IN-CSE now has the complete media description. The streaming session Resource is created AA-Request (AAR) AA-Answer (AAA) Response (updated media -description Data Exchange directly between the NA/ADN Reserve the bearers The MN-CSE creates a streaming session Resource The MN-CSE updates the streaming session Resource

Streaming Session Procedure-Deployment3 MN-CSE1 NA IN-CSE Register with MN_CSE1 CREATE-Streaming-Session (media-description, Target AE-ID, Originating AE-ID, Session-ID) PCRF ADN Register with MN_CSE2 CREATE-Streaming-Session (media-description, Target AE-ID, Originating AE-ID, Session-ID) NOTIFY Target AE-ID Originating AE-ID, Session-ID) Response OK CREATE-Streaming-Session (media-description, Target AE-ID Originating AE-ID, Session-ID) AA-Request (AAR) AA-Answer (AAA) Response (updated media -description Data Exchange directly between the NA/ADN Reserve the bearers MN-CSE2 CREATE-Virtual-Streaming-Session (media-description, Target AE-ID Originating AE-ID, Session-ID) Response OK The streaming session Resource is created The MN-CSE updates the streaming session Resource The streaming session Resource is created

Resources to Support Streaming Sessions A new resource is required to store information relevant to a streaming session. – Supported in MN-CSE, IN-CSE, ASN A new Virtual Resource in IN-CSE is required – This is needed since the IN-CSE is the entity implementing Rx (API) and has to be involved in every streaming session scenario.