1. Issues of <locationPolicy> Discussion
Group Name: ARC
Source: Echo, Huawei,
Meeting Date:
Agenda Item: 3GPP interworking

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

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

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

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

6. Suggested solution
Option 2 6

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

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

9. Thanks for your listening! Q & A