8.1 [_flexNode_] management

8.1.1 Create [flexNode]

This procedure shall be used for creating a [flexNode] resource.

Table 8.1.1-1: [flexNode] CREATE

[flexNode] CREATE
Information in Request message	All parameters defined in TS-0001 [2] table 8.1.2-3 apply with the specific details for: From : Identifier of the IPE that initiates the Request To : The address of the <node> where the [flexNode] resource is intended to be Created Content: The representation of the [flexNode] resource described in clause 5.8.2 in TS-0023 [3].
Processing at Originator before sending Request	According to clause TS-0001 [2] 10.1.2. The Originator should be a Creator IPE that manages the corresponding entity in the Proximal IoT System.
Processing at Receiver	According to clause TS-0001 [2] 10.1.2
Information in Response message	All parameters defined in TS-0001 [2] table 8.1.3-1 apply with the specific details for: Content : Address of the created [flexNode] resource, according to clause TS-0001 [2] 10.1.2
Processing at Originator after receiving Response	According to clause TS-0001 [2] 10.1.2. The originator shall create at least the [dmDeviceInfo], mandatory child of the [flexNode] (see clause 8.3.1).
Exceptions	According to clause TS-0001 [2] 10.1.2

8.1.1.2 Create DM SDT modules

As specified in clause 5.8.2 of TS-0023 [3], the 'flexNode' has at least as mandatory child a 'dmDeviceInfo' ModuleClass The IPE, after creating the [flexNode] resource, shall therefore create a [dmDeviceInfo] <flexContainer> specialization under the [flexNode] .

It also shall create the <flexContainer > specializations that correspond to the DM SDT modules that represent the device management capabilities of the Proximal IoT devices it manages.

For the generic operations on these DM SDT <flexContainer>, children of the [flexNode], see clause 8.2.

8.1.2 Retrieve [flexNode]

This procedure shall be used for retrieving the attributes of a [flexNode] resource.

Table 8.1.2-1: [flexNode] RETRIEVE

[flexNode] RETRIEVE
Information in Request message	All parameters defined in TS-0001 [2] table 8.1.2-3 apply with the specific details for: Content : Void
Processing at Originator before sending Request	According to clause TS-0001 [2] 10.1.3
Processing at Receiver	According to clause TS-0001 [2] 10.1.3
Information in Response message	All parameters defined in TS-0001 [2] table 8.1.3-1 apply with the specific details for: Content: Attributes of the [flexNode] resource as defined in clause TS-0023 [3] 5.8.2.
Processing at Originator after receiving Response	According to clause TS-0001 [2] 10.1.3
Exceptions	According to clause TS-0001 [2] 10.1.3

8.1.3 Update [flexNode]

This procedure shall be used for updating the attributes and the actual data of a [flexNode] resource and its child resources.

Table 8.1.3-1: [flexNode] UPDATE

[flexNode] UPDATE
Information in Request message	All parameters defined in TS-0001 [2] table 8.1.2-3 apply with the specific details for: Content : attributes of the [flexNode] resource as defined in clause TS-0023 [3] 5.8.2 which need be updated, with the exception of the Read Only (RO) attributes that cannot be modified
Processing at Originator before sending Request	According to clause TS-0001 [2] 10.1.4
Processing at Receiver	According to clause TS-0001 [2] 10.1.4 with the following: The Receiver shall check whether the provided attributes of the [flexNode] resource represent a valid request for updating [flexNode] resource
Information in Response message	According to clause TS-0001 [2] 10.1.4
Processing at Originator after receiving Response	According to clause TS-0001 [2] 10.1.4
Exceptions	According to clause TS-0001 [2] 10.1.4

8.1.4 Delete [flexNode ]

This procedure shall be used for deleting an existing [flexNode] resource.

Note

The deletion of the [flexNode] resource is on discretion of the Creator IPE.

Table 8.1.4-1: [flexNode] DELETE

[flexNode] DELETE
Information in Request message	All parameters defined in TS-0001 [2] table 8.1.2-3 apply
Processing at Originator before sending Request	According to clause TS-0001 [2] 10.1.5 The Originator should be a Creator IPE that manages the corresponding entity in the Proximal IoT System.
Processing at Receiver	According to clause TS-0001 [2] 10.1.5
Information in Response message	According to clause TS-0001 [2] 10.1.5
Processing at Originator after receiving Response	According to clause TS-0001 [2] 10.1.5
Exceptions	According to clause TS-0001 [2] 10.1.5