Issues of <locationPolicy> Discussion

Slides:

Advertisements

Similar presentations

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

Advertisements

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.

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

Device Management using mgmtCmd resource Group Name: WG2/WG5 Source: InterDigital Communications Meeting Date: Agenda Item: TBD.

Resource Announcement Procedures Group Name: WG2 Source: Rajesh Bhalla, Hao Wu - ZTE Meeting Date: Agenda Item: TBD.

Announcement Resources ARC Announcement_Issues Group Name: WG2 Source: Barbara Pareglio, NEC Meeting Date: Agenda Item: Input Contribution.

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.

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

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.

Device Management A unified way of managing devices enabled by different management technologies Group Name: WG2/WG5 Source: Huawei Technologies Co., Ltd.

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

Customized Resource Types MAS Group Name: MAS + ARC + PRO WGs Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date:

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.

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.

Supporting Time Series Data Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: Work Item :WI-0033.

Device Management using mgmtCmd resource Group Name: WG2/WG5 Source: InterDigital Communications Meeting Date: Agenda Item: TBD.

3GPP Rel-13 Interworking discussions

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

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.

M2M Service Subscription Profile Discussion Group Name: oneM2M TP #19.2 Source: LG Electronics Meeting Date: Agenda Item:

ARC R02 Modelling operations – problem statement and proposal Group Name: ARC#19.3 Source: Joerg Swetina, NEC,

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

3GPP SCEF Interworking Discussions

LWM2M Interworking Proxy Procedures ARC Considerations

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

Issues of Current Access Control Rule and New Proposal Introduction Group Name: ARC 21 Source: Wei Zhou, Datang, Meeting Date:

Adding Non-blocking Requests Contribution: oneM2M-ARC-0441R01R01 Source: Josef Blanz, Qualcomm UK, Meeting Date: ARC 7.0,

Authorization Architecture Discussion Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 28 MAY, 2014 Agenda.

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 Execute Group Name: WG2/WG5 Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD.

Possible Solution of Interworking between oneM2M and OSGi

Discussion about Interoperability (&versioning) Group Name: PRO & ARC Source: FUJITSU Meeting Date: Agenda Item: TS-0004.

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

Resource subscription using DDS in oneM2M

3GPP MBMS protocol stack

Service Framework Proposal

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

Service Enabled AE (SAE)

End-to-End Security for Primitives

Group multicast fanOut Procedure

2nd Interoperability testing issues

3GPP interworking in R3 Group Name: ARC

Possible options of using DDS in oneM2M

Proposed design principles for modelling interworked devices

oneM2M Service Layer Protocol Version Handling

3GPP Rel-13 Interworking discussions

Proximal IoT Interworking solution discussion

3GPP Interworking Abstraction

Group multicast Group Name: ARC

Considering issues regarding handling token

LWM2M Interworking with <mgmtObj> Resources

CMDH Refinement Contribution: oneM2M-ARC-0397R01

MinitorEvent(UE_Reachability)

Service Layer Dynamic Authorization [SLDA]

3GPP V2X Interworking Potential Impact

3GPP Interworking and use of <schedule> resource

Summary of the MAF and MEF Interface Specification TS-0032

oneM2M interop 6 action point

Presentation transcript:

Issues of <locationPolicy> Discussion Group Name: ARC Source: Echo, Huawei, echo.xubei@huawei.com Meeting Date: 2017-06-22 Agenda Item: 3GPP interworking

What oneM2M support about <locationPolicy> CSE/AE When locationSource is Network-based method, locationUpdatePeriod is higher than 0 second, the Hosting CSE shall periodically transform the location-acquisition request into Location Server request. When locationSource is Network-based method, locationUpdatePeriod is 0 or not defined, the Hosting CSE shall transform the location-acquisition request into Location Server request only when a retrieval request is triggered. 2

The issues1 about <locationPolicy> CSE/AE When locationSource is Network-based method, locationUpdatePeriod is 0 or not defined, the Hosting CSE shall transform the location-acquisition request into Location Server request only when a retrieval request is triggered. Issue: the retrieval procedure is not specified in TS-0001 & TS-0004. 3

Option 1: Originator Retrieves <container> Mca/Mcc Targeted CSE/AE Mca/Mcc Location CSE Mcn Network Location Server 1 Retrieve <latest> of <container> Request 2 Retrieve <locationPolicy> Request by locationID 3b Return Error if locationUpdatePeriod > 0 3 Transform the location-acquisition request based on targetedID and locationServer 4 Return the location Information of targetedID 5 Create <contentInstance> of the <container> Request 6 Create Response 7 Retrieve Response 8 Return retrieve Result Problem 1: If the there is locationID of <CSE>/<AE>, the targeted CSE/AE shall transfer the retrieve request to location CSE every time even the locationUpdatePeriod is higher than 0. Problem 2: Step2-Step7 between Targeted CSE/AE and Location CSE are redundancy and inefficient. 4

Option 2: Originator Retrieves <locationPolicy> Mca/Mcc Location CSE Mca/Mcc Targeted CSE/AE Mcn Network Location Server 1 Retrieve <locationContainerID> of <locationPolicy> Request 2 Transform the location-acquisition request based on targetedID and locationServer 3 Return the location Information of targetedID 4 Return retrieve Result <contentInstance> 5 Create <contentInstance> of the <container> Request 6 Create Response Note 1: The locationContainerID is attribute of <locationPolicy>, it’s not normal attribute retrieval procedure. Note 2: Step4: Location CSE shall return only one and latest <contentInstance>. 5

Suggested solution Option 2 6

The issues2 about <locationPolicy> If the different Originators create different <locationPolicy> resources for the same targeted node, how to update the location container information? Originator1 Location CSE Targeted CSE/AE Originator2 <CSEBase> <locationPolicy> <locationPolicy> 7

<CSEBase>/<AE> Solution: <CSEBase>/<AE> <CSEBase> When targeted the same node, the <locationPolicy> resources are different, the containers should be different as well. 8

Thanks for your listening! Q & A