6.14 _<reasoningRules>_ Operations

6.14.1 Introduction

A <reasoningRules> resource can be used to store a set of related reasoning rules (e.g. for supporting a particular application). A <reasoningRules> resource is a child resource of the <semanticRuleRepository> resource. By performing the CRUD operations on the <reasoningRules> resources, various reasoning rules (e.g., user-defined reasoning rules based on business logic) can be created, discovered, retrieved, updated and deleted inside the oneM2M system.

6.14.2 Create <reasoningRules>

This procedure is used for creating a <reasoningRules> resource as described in Table 6.14.2-1.

Table 6.14.2-1: <reasoningRules> CREATE

<reasoningRules> CREATE	<reasoningRules> CREATE
Associated Reference Point	Mca, Mcc and Mcc'
Information in Request message	All parameters defined in Table 8.1.2-3 in TS-0001 [1] apply with the specific details for: Content : The resource content provides the information as defined in the resource definition of <reasoningRules> resource.
Processing at Originator before sending Request	According to clause 10.1.2 in oneM2M TS-0001 in [1].
Processing at Receiver	According to clause 10.1.2 in oneM2M TS-0001 in [1].
Information in Response message	All parameters defined in table 8.1.3-1 in [i.3] apply with the specific details for: Content : Address of the created <reasoningRules> resource, according to clause 10.1.2 in [i.3].
Processing at Originator after receiving Response	According to clause 10.1.2 in oneM2M TS-0001 in [1].
Exceptions	According to clause 10.1.2 in oneM2M TS-0001 in [1].

6.14.3 Retrieve <reasoningRules>

This procedure is used for retrieving the attributes of a <reasoningRules> resource as described in Table 6.14.3-1.

Table 6.14.3-1: <reasoningRules> RETRIEVE

<reasoningRules> RETRIEVE	<reasoningRules> RETRIEVE
Associated Reference Point	Mca, Mcc and Mcc'.
Information in Request message	All parameters defined in table 8.1.2-3 in [1] apply.
Processing at Originator before sending Request	According to clause 10.1.3 in oneM2M TS-0001 in [1].
Processing at Receiver	According to clause 10.1.3 in oneM2M TS-0001 in [1].
Information in Response message	All parameters defined in Table 8.1.3-1 in [1] apply with the specific details for: Content : Attributes of the <reasoningRules> resource.
Processing at Originator after receiving Response	According to clause 10.1.3 in oneM2M TS-0001 in [1].
Exceptions	According to clause 10.1.3 in oneM2M TS-0001 in [1].

6.14.4 Update <reasoningRules>

This procedure is used for updating the attributes of a <reasoningRules> resource as described in Table 6.14.4-1.

Table 6.14.4-1: <reasoningRules> UPDATE

<reasoningRules> UPDATE	<reasoningRules> UPDATE
Associated Reference Point	Mca, Mcc and Mcc'
Information in Request message	All parameters defined in Table 8.1.2-3 in [1] apply with the specific details for: Content : Attributes of the <reasoningRules> resource to be updated.
Processing at Originator before sending Request	According to clause 10.1.4 in oneM2M TS-0001 in [1].
Processing at Receiver	According to clause 10.1.4 in oneM2M TS-0001 in [1].
Information in Response message	According to clause 10.1.4 in oneM2M TS-0001 in [1].
Processing at Originator after receiving Response	According to clause 10.1.4 in oneM2M TS-0001 in [1].
Exceptions	According to clause 10.1.4 in oneM2M TS-0001 in [1].

6.14.5 Delete <reasoningRules>

This procedure is used for deleting a <reasoningRules> resource as described in table 6.14.5-1.

Table 6.14.5-1: <reasoningRules> DELETE

<reasoningRules> DELETE	<reasoningRules> DELETE
Associated Reference Point	Mca, Mcc and Mcc'
Information in Request message	All parameters defined in Table 8.1.2-3 in [1] apply.
Processing at Originator before sending Request	According to clause 10.1.5 in oneM2M TS-0001 in [1].
Processing at Receiver	According to clause 10.1.5 in oneM2M TS-0001 in [1].
Information in Response message	According to clause 10.1.5 in oneM2M TS-0001 in [1].
Processing at Originator after receiving Response	According to clause 10.1.5 in oneM2M TS-0001 in [1].
Exceptions	According to clause 10.1.5 in oneM2M TS-0001 in [1].