6.3 Modbus IPE registration

Figure 6.3-1 shows the device registration call flow:

1. The IPE shall request to create an <AE> resource on the Hosting CSE to register the Modbus master collocated on the IPE.
2. The Hosting CSE shall evaluate the request, performs the appropriate checks, and creates the <AE> resource. The Hosting CSE shall respond with the successful result of <AE> resource creation, otherwise it responds with an error.
3. Modbus devices are registered at Modbus IPE, in particular Modbus interworking information (slave id, registers type, address, length) are defined in accordance with provided device datasheet.
4. Modbus IPE shall send corresponding requests to a CSE to create resources which were from SDT schemas as described in clause 6.2.3. For all <flexContainer> resources, the containerDefinition attribute is mandatory. The contentSize attribute is calculated by the Hosting CSE. The customAttributes of the <flexContainer> resources should be specified if they are mandatory for that <flexContainer>. Each resource creation is originated by the Modbus-IPE in a separate request for each resource.
5. After verifying the privileges and the given attributes, the Hosting CSE shall create each resource.
6. The Hosting CSE shall respond with the successful result for each created resource, otherwise it shall respond with an error.

Figure 6.3-1: Device registration call flow