Abstract: Aspects of the disclosure provide a system having a memory area associated with a computing device and a processor. The processor executes to classify device panel descriptors and location descriptors according to associated device instances. The processor generates device panel objects using the classified device panel descriptors and location descriptors. A schema comprising device panel locations and adjacency relationship information is populated for the computing device based on the generated device panel objects. The processor provides the populated schema as dynamic device properties to one or more operations executing on the computing device.

Abstract: Aspects of the disclosure provide a system having a memory area associated with a computing device and a processor. The processor executes to classify device panel descriptors and location descriptors according to associated device instances. The processor generates device panel objects using the classified device panel descriptors and location descriptors. A schema comprising device panel locations and adjacency relationship information is populated for the computing device based on the generated device panel objects. The processor provides the populated schema as dynamic device properties to one or more operations executing on the computing device.

Abstract: Aspects of the disclosure provide a system having a memory area associated with a computing device and a processor. The processor executes to classify device panel descriptors and location descriptors according to associated device instances. The processor generates device panel objects using the classified device panel descriptors and location descriptors. A schema comprising device panel locations and adjacency relationship information is populated for the computing device based on the generated device panel objects. The processor provides the populated schema as dynamic device properties to one or more operations executing on the computing device.

Abstract: Techniques for monitoring presence of a remote device at Layer 2 that allow reducing power consumption without compromising the device's availability. A device that pairs with a remote wireless device may establish a Layer 3 connection, such as an IP connection, to the remote device to provide services to a user. The Layer 3 connection may be formed over a Layer 2 connection via an access point or as a peer-to-peer wireless connection between the devices. When the Layer 3 connection is not actively used to access the remote device, the Layer 3 connection and the supporting Layer 2 connection (e.g., WI-FI, WI-FI DIRECT™ or BLUETOOTH®) may be terminated and presence of the remote device may be monitored using a Layer 2 device discovery mechanism. The Layer 2 and Layer 3 connections to the device may be reestablished when use of the remote device is desired.

Abstract: Aspects of the disclosure provide a system having a memory area associated with a computing device and a processor. The processor executes to classify device panel descriptors and location descriptors according to associated device instances. The processor generates device panel objects using the classified device panel descriptors and location descriptors. A schema comprising device panel locations and adjacency relationship information is populated for the computing device based on the generated device panel objects. The processor provides the populated schema as dynamic device properties to one or more operations executing on the computing device.

Abstract: Techniques for monitoring presence of a remote device at Layer 2 that allow reducing power consumption without compromising the device's availability. A device that pairs with a remote wireless device may establish a Layer 3 connection, such as an IP connection, to the remote device to provide services to a user. The Layer 3 connection may be formed over a Layer 2 connection via an access point or as a peer-to-peer wireless connection between the devices. When the Layer 3 connection is not actively used to access the remote device, the Layer 3 connection and the supporting Layer 2 connection (e.g., WI-FI, WI-FI DIRECT™ or BLUETOOTH®) may be terminated and presence of the remote device may be monitored using a Layer 2 device discovery mechanism. The Layer 2 and Layer 3 connections to the device may be reestablished when use of the remote device is desired.

Abstract: Techniques for monitoring presence of a remote device at Layer 2 that allow reducing power consumption without compromising the device's availability. A device that pairs with a remote wireless device may establish a Layer 3 connection, such as an IP connection, to the remote device to provide services to a user. The Layer 3 connection may be formed over a Layer 2 connection via an access point or as a peer-to-peer wireless connection between the devices. When the Layer 3 connection is not actively used to access the remote device, the Layer 3 connection and the supporting Layer 2 connection (e.g., WI-FI, WI-FI DIRECT™ or BLUETOOTH®) may be terminated and presence of the remote device may be monitored using a Layer 2 device discovery mechanism. The Layer 2 and Layer 3 connections to the device may be reestablished when use of the remote device is desired.

Abstract: Techniques for monitoring presence of a remote device at Layer 2 that allow reducing power consumption without compromising the device's availability. A device that pairs with a remote wireless device may establish a Layer 3 connection, such as an IP connection, to the remote device to provide services to a user. The Layer 3 connection may be formed over a Layer 2 connection via an access point or as a peer-to-peer wireless connection between the devices. When the Layer 3 connection is not actively used to access the remote device, the Layer 3 connection and the supporting Layer 2 connection (e.g., WI-FI, WI-FI DIRECT™ or BLUETOOTH®) may be terminated and presence of the remote device may be monitored using a Layer 2 device discovery mechanism. The Layer 2 and Layer 3 connections to the device may be reestablished when use of the remote device is desired.

Abstract: Techniques for monitoring presence of a remote device at Layer 2 that allow reducing power consumption without compromising the device's availability. A device that pairs with a remote wireless device may establish a Layer 3 connection, such as an IP connection, to the remote device to provide services to a user. The Layer 3 connection may be formed over a Layer 2 connection via an access point or as a peer-to-peer wireless connection between the devices. When the Layer 3 connection is not actively used to access the remote device, the Layer 3 connection and the supporting Layer 2 connection (e.g., WI-FI, WI-FI DIRECT™ or BLUETOOTH®) may be terminated and presence of the remote device may be monitored using a Layer 2 device discovery mechanism. The Layer 2 and Layer 3 connections to the device may be reestablished when use of the remote device is desired.

Abstract: Techniques for monitoring presence of a remote device at Layer 2 that allow reducing power consumption without compromising the device's availability. A device that pairs with a remote wireless device may establish a Layer 3 connection, such as an IP connection, to the remote device to provide services to a user. The Layer 3 connection may be formed over a Layer 2 connection via an access point or as a peer-to-peer wireless connection between the devices. When the Layer 3 connection is not actively used to access the remote device, the Layer 3 connection and the supporting Layer 2 connection (e.g., WI-FI, WI-FI DIRECT™ or BLUETOOTH®) may be terminated and presence of the remote device may be monitored using a Layer 2 device discovery mechanism. The Layer 2 and Layer 3 connections to the device may be reestablished when use of the remote device is desired.

Abstract: Techniques for monitoring presence of a remote device at Layer 2 that allow reducing power consumption without compromising the device's availability. A device that pairs with a remote wireless device may establish a Layer 3 connection, such as an IP connection, to the remote device to provide services to a user. The Layer 3 connection may be formed over a Layer 2 connection via an access point or as a peer-to-peer wireless connection between the devices. When the Layer 3 connection is not actively used to access the remote device, the Layer 3 connection and the supporting Layer 2 connection (e.g., WI-FI, WI-FI DIRECT™ or BLUETOOTH®) may be terminated and presence of the remote device may be monitored using a Layer 2 device discovery mechanism. The Layer 2 and Layer 3 connections to the device may be reestablished when use of the remote device is desired.

Abstract: Techniques for monitoring presence of a remote device at Layer 2 that allow reducing power consumption without compromising the device's availability. A device that pairs with a remote wireless device may establish a Layer 3 connection, such as an IP connection, to the remote device to provide services to a user. The Layer 3 connection may be formed over a Layer 2 connection via an access point or as a peer-to-peer wireless connection between the devices. When the Layer 3 connection is not actively used to access the remote device, the Layer 3 connection and the supporting Layer 2 connection (e.g., WI-FI, WI-FI DIRECT™ or BLUETOOTH®) may be terminated and presence of the remote device may be monitored using a Layer 2 device discovery mechanism. The Layer 2 and Layer 3 connections to the device may be reestablished when use of the remote device is desired.

Abstract: Techniques for monitoring presence of a remote device at Layer 2 that allow reducing power consumption without compromising the device's availability. A device that pairs with a remote wireless device may establish a Layer 3 connection, such as an IP connection, to the remote device to provide services to a user. The Layer 3 connection may be formed over a Layer 2 connection via an access point or as a peer-to-peer wireless connection between the devices. When the Layer 3 connection is not actively used to access the remote device, the Layer 3 connection and the supporting Layer 2 connection (e.g., WI-FI, WI-FI DIRECT™ or BLUETOOTH®) may be terminated and presence of the remote device may be monitored using a Layer 2 device discovery mechanism. The Layer 2 and Layer 3 connections to the device may be reestablished when use of the remote device is desired.

Abstract: Techniques for monitoring presence of a remote device at Layer 2 that allow reducing power consumption without compromising the device's availability. A device that pairs with a remote wireless device may establish a Layer 3 connection, such as an IP connection, to the remote device to provide services to a user. The Layer 3 connection may be formed over a Layer 2 connection via an access point or as a peer-to-peer wireless connection between the devices. When the Layer 3 connection is not actively used to access the remote device, the Layer 3 connection and the supporting Layer 2 connection (e.g., WI-FI, WI-FI DIRECT™ or BLUETOOTH®) may be terminated and presence of the remote device may be monitored using a Layer 2 device discovery mechanism. The Layer 2 and Layer 3 connections to the device may be reestablished when use of the remote device is desired.

Abstract: A unified architecture for enabling remote access to a network is provided. The network may comprise, as examples, a virtual private network (VPN) and/or a peer-to-peer network. In one embodiment, the architecture includes components installed on a client device/node and a gateway/supernode. Components implemented on the client device may facilitate access in a manner similar to that of a traditional VPN, while components on the gateway may facilitate access in a manner similar to an application proxy. Communication between the client device and gateway may occur, as an example, via a Secure Sockets Layer (SSL) communication protocol.

Abstract: A namespace management module utilizes a persistent reservation store that associates URI namespaces with one or more permissions. The reservation store can contain a number of reservation entries that each include a URI identifying a URI namespace and a corresponding Access Control List (“ACLs”) that includes permissions for the identified URI namespace. When a request to register a URI namespace is received, the permissions of an appropriate ACL can be checked to determine if the registration is approved. When a resource request is received, permissions of the ACLs can also be checked to determine if the resource request should be routed to a registered process. Preemptive wildcards can be included in aggregated URIs to identify aggregated URI namespaces. Aggregated URIs can be included in registration requests to override the registration of unauthorized processes.

Abstract: A namespace management module utilizes a persistent reservation store that associates URI namespaces with one or more permissions. The reservation store can contain a number of reservation entries that each include a URI identifying a URI namespace and a corresponding Access Control List (“ACLs”) that includes permissions for the identified URI namespace. When a request to register a URI namespace is received, the permissions of an appropriate ACL can be checked to determine if the registration is approved. When a resource request is received, permissions of the ACLs can also be checked to determine if the resource request should be routed to a registered process. Preemptive wildcards can be included in aggregated URIs to identify aggregated URI namespaces. Aggregated URIs can be included in registration requests to override the registration of unauthorized processes.