SDO11 — Configuration interface

The Configuration interface provides operations to ‘set’ or ‘remove’ ‘device’ or ‘service’ profiles (setDeviceProfile(…), addServiceProfile(…), removeDeviceProfile(), removeServiceProfile(…)). We can implement them without problem but the problem is the real implication or the usage of such operations. An SDO may represent a device. We must clearly define in what circumstances do we need to remove the device profile or set the new profile. Similarly an SDO may provide one or more services. How can it provide new services in reality if the device it is representing is the same? How is this new service instantiated? Let’s look at each of these operations in more detail: • setDeviceProfile(…) o Overwrite old DeviceProfile with the new Device Profile. o What else should be done to reflect the changes in the DeviceProfile? • removeDeviceProfile(…) o Removes the existing DeviceProfile o What else should be done to reflect that there is no DeviceProfile? For example if the SDO represents ‘TV’, is this method invoked when real hardware device (‘TV’) is temporarily not available? Moreover, what does it mean when there is no ‘DeviceProfile’ but the SDO represents ‘TV’? Does it still continue to provide services it was providing? • addServiceProfile(…) o Adds new service profile o Instantiate the service An SDO represents a device (eg. ‘TV’) or a service. A ‘TV’ or any other SDOs most probably will not have to provide additional service during its runtime. • removeServiceProfile(…) o stop the service o remove service profile o What else does it need to do? Should it send message to all SDOs that are using this service? Most likely SDO can only internally invoke such operations when required. Other SDO should not be allowed to invoke such operations.