TS-0001 and TS-0004 contradicts on cancellation procedure of software operation
In section 10.2.28.1 of TS-0001, text for the cancellation procedure of software operation indicates that when update request from AE updates the campaignEnabled to FALSE, the Hosting CSE may choose to let the operation finish or attempt to cancel the operation. After that TS-0001 says:
If the Hosting CSE is not able to successfully cancel all the software operations, the Hosting CSE shall set the campaignStatus attribute to a value of “STATUS_NOT_CANCELLABLE”.
The above mentioned paragraph does not explain anything about sending back response to the AE. Furthermore, if we consider TS-0001, Step 2 of Figure 10.2.28.2-1: Software Management by a CSE, it indicates that response will be sent to AE after updation of . So, according to TS-0001 it seems like AE is sending an Asynchronous UPDATE request.
INSERT REFERENCE TO THE CR AND CLAUSE HERE FOR TS004 Now, on the other hand in TS-0004 the UPDATE procedure which triggers the cancellation of software operation states that:
10) If the value of the campaignEnabled attribute in the request is FALSE and the value of the campaignEnabled attribute of the targeted <softwareCampaign> resource is TRUE, and the value of the campaignStatus attribute of the targeted <softwareCampaign> resource is “INITIATED”, then the Receiver shall set the value of the campaignStatus attribute of the targeted <softwareCampaign> resource to “CANCELLING” and attempt to cancel the software campaign as described in clause 10.2.28 of oneM2M TS-0001 [6]. If the Receiver is unable to cancel the software campaign, it shall return a response primitive with a Response Status Code indicating "CANCELLATION_FAILED" error.
According to TS-0004, Hosting CSE sends a response to the AE after performing the whole cancellation procedure. So, TS-004 implies that the UPDATE procedure follows a Synchronous request.