Group multicast Group Name: ARC

Slides:

Advertisements

Similar presentations

Call for test suites Group Name: REQ Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD.

Advertisements

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

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

Problem of Current Notification Group Name: ARC WG Source: Heedong Choi, LG Electronics, Meeting Date: ARC 9.0 Agenda Item: TBD.

Problem of non-Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.0 Agenda Item: TBD.

REQ WG Reuse of underlying networks, 3GPP

REQ WG Reuse of underlying networks, 3GPP

Discussion on constraint device optimization Group Name: ARC Source: Jiaxin (Jason) Yin, Huawei Technologies Co., Ltd., Meeting Date:

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

OneM2M Interop Test Event Announcement Group Name: TST 16.2 Source: Jiaxin Yin, Huawei Technologies Co., Ltd. Meeting Date: Agenda Item: TBD.

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

Discussion on the problem of non- Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.2.

App-ID Discussion Group Name: ARC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 31 July 2014 Agenda Item: TBD.

OneM2M Interop Test Event Announcement Group Name: TST 16.2 Source: Jiaxin Yin, Huawei Technologies Co., Ltd. Meeting Date: Agenda Item: TBD.

OneM2M Interop Test Event Announcement Group Name: TST 16.2 Source: Jiaxin Yin, Huawei Technologies Co., Ltd. Meeting Date: Agenda Item: TBD.

Supporting long polling Group Name: ARC WG Source: SeungMyeong, LG Electronics, Meeting Date: x-xx Agenda Item: TBD.

Discussion on the problem of non- Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.2.

Node-Specific Resource Group Name: ARC&MAS Source: LGE, Meeting Date: Agenda Item: Contribution.

WG 3 Progress Report at TP15 Group Name: oneM2M TP15 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

3GPP Rel-13 Interworking discussions

Issues pertaining to IOP test Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd. Meeting Date: Agenda Item: TBD.

E2EKey Resource Group Name: SEC WG Source: Qualcomm Inc., Wolfgang Granzow & Phil Hawkes Meeting Date: SEC#20.3, Agenda Item: End-to-End Security.

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

Planning for the test event Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item:

WG1 status report to TP#21 Group Name: oneM2M TP21 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#21, Item 10.4,

Communication Method Group Name: ARC Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD.

3GPP SCEF Interworking Discussions

Call for input from WGs on things to test Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date:

WG5 - MAS Progress Report at TP #8 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.

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:

DM Execute Group Name: WG2/WG5 Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD.

WG1 - REQ Progress Report at TP #11 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chairs Meeting Date: to Agenda Item: TP#11,

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

3GPP R13 Small Data Delivery

Managing Retransmission Timers in Sleep Mode

oneM2M Requirements for SCEF northbound API

3GPP MBMS protocol stack

Provisional Architecture for oneM2M

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

SCEF northbound API Analysis

Proximal IoT Interworking discussion

Group multicast fanOut Procedure

Group multicast fanOut Procedure

WG2 - ARC TP#29 Status Report

3GPP interworking in R3 Group Name: ARC

Managing Retransmission Timers in Sleep Mode

Issues of <locationPolicy> Discussion

NIDD Discussion Points

Proposed design principles for modelling interworked devices

MAF&MEF Interface Specification discussion of the next steps

3GPP Rel-13 Interworking discussions

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

Invite IIC testbeds to oneM2M interops

WG2 - ARC TP#29 Status Report

Proximal IoT Interworking solution discussion

Discussion to clarify online/offline behavior

3GPP Interworking Abstraction

ARC Proposed design principles for modelling services, datapoints and operations Group Name: ARC Source: Joerg Swetina, NEC

Aggregation of notification

Discussion on feature catalogue

MinitorEvent(UE_Reachability)

3GPP V2X Interworking Potential Impact

3GPP Interworking and Multicast retransmission

Presentation transcript:

Group multicast Group Name: ARC Source: Jiaxin Yin, Huawei Technologies Co., Ltd. yinjiaxin@huawei.com Meeting Date: 2016-10-17 Agenda Item: TBD

Background oneM2M does not support the utilizing multicast capability from the underlying network if supported. The underlying network could be 3GPP network or binding protocols like CoAP etc. The discussion is to kick off the question how to support multicast group by oneM2M? The contribution is the presentation show for ARC-2016-0455-group_multicast

Multicast Group case1 None of the group member have multicast capability, the same as before: not multicast group Group create request CSE Check Multicast capability one by one ASN1 ASN2 ASN3 ASN4 ASN5 One Group, no multicast group

Subgroup management case2 All the group member have the same multicast capability: eg.3GPP MBMS, there is one subgroup. Group create request CSE Check Multicast capability one by one ASN1 ASN2 ASN3 ASN4 ASN5 One multicast Group: 3GPP MBMS group

Subgroup management case3 Part of the group member have multicast capability：eg.3GPP MBMS; the others do not. Group create request CSE Check Multicast Capability one by one ASN1 ASN2 ASN3 ASN4 ASN5 One multicast group：3GPP MBMS multicast group

Subgroup management case4 Some of the group member have multicast capability：eg. 3GPP MBMS; the others have the IP multicast capability. Group create request CSE Check Multicast Capability one by one ASN1 ASN2 ASN3 ASN4 ASN5 Multicast group 1：3GPP MBMS multicast Multicast group 2：IP multicast

Resource structure Group The <multicastGroup> resource is for the multicast of the group members. The multicastGroup contains a subset of the group members that belongs to one network and same multicast capability segment. multicastGroup multicastType multicastAddress memberList CSEbase fanOutURI parentGroup The <ParentGroup> resource is to indicate that if the CSE is part of a multicast group. multicastAddress memberList fanOutURI responseURI

Group create procedure AE IN-CSE ASN1 ASN2 ASN3 ASN4 ASN5 Create group Determines that ASN1,2,3 belongs to the same multicast group Allocate multicastAddress and fanOutURI Create multicast Try to add itself into the multicast group success success

Group fanout procedure AE IN-CSE SCEF MulticastServer ASN1 ASN2 ASN3 Address fanout Req Check the multicast group type Case A: multicastType = 3GPP MBMS Group message delivery using MBMS defined TS23682 Case B: multicastType = IP Multicast Send fanout message to the multiCastAddress Multicast using using the mapping between fanOutURI and memberIDs Success Rsp Aggregate the member responses Success Rsp

Questions and comments