ISO/IEC29341-12-2:2015(E) 2. Device Definitions 2.1. Device Type The following device type identifies a device that is compliant with this template: urn:schemas-upnp-org:device: RemoteUServerDevice:l 2.2. Device Model It is recommended that RemoteUIServerDevice be implemented with support for securing UPnP actions. It is also recommended that securing of UPnP m action is done using the DeviceSecurity service as defined by the RemoteUIServerDevice implementationorin adevicethat encompasses theRemoteUIServerDevice.Thesetwo models are described below. 2.2.1.Description ofDeviceRequirements The following table briefly describes the service used in RemoteUIServerDevice. Table1:RemoteUiServerDeviceServiceDescriptions Service Name Service Description RemoteUIServer Allows for basic discovery of available and remotable user interfaces DeviceSecurity Actions for taking ownership, configuring access control, establishing secure sessions, and invoking secure actions. 2.2.1.1.DeviceSecurity withinRemoteUIServerDevice This model is typically applicable to physical devices that need DeviceSecurity functionality (including device ownership and access control) to be used only by the RemoteUIServerDevice. In this case, products that expose devices of the type urn:schemas-upnp-org:device:RemoteUiServerDevice:lmustimplement minimum version numbers of the required service specified in the table below. Table2:DeviceRequirementsforstand-aloneRemoteUiServerDevice DeviceType ServiceType Root Req. Req. Service ID? Opt." Opt." RemoteUIServerDevice: l Yes R RemoteUIServer: 1 R RemoteUIServer DeviceSecuirty! 0 DeviceSecurity Non-standard services X To be defined by vendor embeddedbyanUPnPvendor go here. R = Required, O = Optional, X = Non-standard. 2 Prefixed by urn:upnp-org:serviceld Relationshipbetween Services 2 ISO/IEC 2015 - All rights reserved ISO/IEC29341-12-2:2015(E) Figure 1 shows the logical structure of the device and services defined by the working group for UPnP rx technology enabled Remote UI servers. RemoteUiServerDevice RemoteUIServerService required DeviceSecurity Figure l:DeviceSecurity within RemoteUiServerDevice 2.2.1.2.DeviceSecurity outside RemoteUIServerDevice This model is typically applicable to physical devices that implement Remote UI server functionality, but the RemoteUIServerDevice may use DeviceSecurity that is already part of another device. An example of this would be where_urn:schemas-upnp-org:device: RemoteUIServerDevice:1 is implemented inside a device of the type urn:schemas-upnp-org:device: BasicDevice:l. The BasicDevice in this case contains the DeviceSecurity service that may be used by another UPnP m device e.g., MediaRenderer. The implementation of RemoteUIServerDevice must contain the minimum version numberof the service specified in the table below. Table3:DeviceRequirementsforembeddedRemoteUiServerDevice DeviceType Root Req. ServiceType Req. Service ID? or Opt. Opt.1 RemoteUIServerDevice:l Yes R RemoteUIServer:1 R RemoteUIServer Non-standard services X Tobedefined byvendor embedded by an UPnP vendor go here. R = Required, O = Optional, X = Non-standard. 2 Prefixed by urn:upnp-org:serviceld: Relationships between Services Figure 2 shows the logical structure of the device and services defined by the working group for UPnP Tx technology enabled Remote UI servers that may use the DeviceSecurity service for other UPnP m devices contained in the same physical device.RemoteUiServerservice may bedependent on theDeviceSecurity service for providing access control to the actions defined in the services. ISO/IEC 2015-All rights reserved 3 ISO/IEC 29341-12-2:2015(E) Basic Device (example) RemoteUiServerDevice RemoteUiServerService required DeviceSecurity Figure2:Example of DeviceSecurity outsideRemoteUiServerDevice 2.2.2.Relationships BetweenServices The dependencies between the services are listed in the above section under the possible models of implementing services inRemoteUIServerDevice. 2.3. Theory of Operation It