The Set‐up Phase. In order for the actions of Section 6.4.1 to be carried out, there must be a set-up phase – which may indeed be entered many times. Again it is difficult to generalise, but we will describe a typical set-up phase for the Smart Buildings, which are the main validation examples in IoT6. We assume that there is a Master Management System (MMS), which can call many generic AI applications. These are stored in a database, with a Handle to the applicatio stored. During the building installation phase, several databases are set up. One is the Model Configuration (MC) database. This is the database of the building, based on some model of the building. For each room, exact devices are stated. For each device, its exact description is given – including possibly authentication information buil into the device. From this authentication information, and for example, network IPv6 address, a Device Authentication Token (DAT) is constructed. It should be noted that some of the databases may still reference others. For example, the configuration database of the building may just state that each room has a door sensor and door actuator. A further database gives the actual model identifier and serial number of each component. The model identifier may actually be the Electronic Products Code [46] of the component. If there is a fault, and a component is replaced, the repairer would be obliged to put a new EPC into this database. During the configuration phase, a HANDLE registration phase is entered which assigns a Handle to each room and to each device; this Handle may be algorithmically constructed in a manner similar to the Glowbal system [47]. There are two differences: First, the construction is of an Identifier, not a network address name; thus it is not stored in an openly searchable DNS but is stored in only a HANDLE store that requires authorisation. Secondly the Handle stores data about the device or room – possibly including authentication tokens. During this phase, one associates authorisation rights to each Handle. One may also a sociate processing Handles. For example, one may define a technology-dependent process to construct the data to be sent to a device; this can be defined in the Handle of the Device as of type nextprocess, which in turn is a complete process – including requiring an authorisation token to be activated. The Handle for each device will also include a networkaddress. While this may again be defined algorithmically, this algorithm needs to tak...
