To make my point more clear, I have further clarification below:
Reference documents:
[1] TS-0001-Functional_Architecture-V1_6_1_2
[2] TS-0004_Service_Layer_Core_Protocol_Specification-V_1_0_1
-------- --------------- --------------
| AE |-------------->| Hosting-CSE |--------------->| Remote-CSE |
-------- --------------- --------------
Mca Mcc
AE sends create <AE> resource request to Hosting-CSE, with announeTo attribute (at) set to Remote-CSE, and all MA, OA attributes in announedAttributes (aa).
On Mca interface, to comply with Table 7.3.5.1-2 and Table 7.3.5.1-3 in [2], CREATE request includes these attributes in resource:
accessControlPolicyIDs (acpi)
expirationTime (et)
labels (lbl)
announceTo (at)
announcedAttribute (aa)
appName (apn)
app-ID (api)
pointOfAccess (poa)
ontologyRef (or)
where aa includes these MA and OA attributes, according to Table 9.6.5-2 in [1]:
resoureID (ri)
resourceName (rn)
expirationTime (et)
accessControlPolicyIDs (acpi)
labels (lbl)
appName (apn)
app-ID (api)
AE-ID (aei)
pointOfAccess (poa)
ontologyRef (or)
nodeLink (nl)
When Hosting-CSE receives the request, it follows description in Section 7.2.3.9 in [2]:
"Compose the CREATE Request primitive as follows:
- Link is set to the URI of the original resource.
- If accessControlPolicyIDs of the original resource is not present, accessControlPolicyIDs is set to the same value with the parent resource or from the local policy of the original resource.
- Attributes marked with MA and attributes marked with OA that are included in the announcedAttribute attribute. Such attributes shall be present in the original resource and set to same value as the original resource."
Then on Mcc, Hosting-CSE sends AEAnnc CREATE request, with attributes in resource specified in aa. Note that ri, rn, acpi and aei have values that would be meaningful only to Hosting-CSE, as these attributes are locally set by Hosting-CSE.
When Remote-CSE receives the AEAnnc CREATE request from Hosting-CSE, as there is no explicit CRUD description for <AEAnnc> resource in [2], Remote-CSE would eithe check the CREATE request against <AE> Table 7.3.5.1-2 and Table 7.3.5.1-3 in [2], or there is no check.Obviously check against <AE> Table 7.3.5.1-2 and Table 7.3.5.1-3 would fail, because ri, rn, acpi are marked NotPresent (NP) but they are in request.
If Remote-CSE skips the check, and takes ri, rn and acpi values as they are in request, then they would have a chance to conflict with existing resources on Remote-CSE, since ri is only relative to CSE only. Of course <AE> and <AEAnnc> can start with 'S' character and becomes Service-Provider level resource, but it won't help for other announcable resources.
Above is my observation based on [1] and [2].
Regards,
Ray Xu
########################################################################
To unsubscribe from the oneM2M_TechQuestions list, click the following link:
https://list.etsi.org/scripts/wa.exe?SUBED1=oneM2M_TechQuestions&A=1
|
